Enhance GitHub Integration for Supabase to Support Full config.toml Configuration

The current GitHub integration for Supabase only supports deploying functions and migrations as code, but does not fully utilize the config.toml for the rest of the project configuration. This limits the ability to have the entire Supabase project configured as code, requiring additional manual or custom CI/CD setups. Feature Request Add options in the GitHub integration to selectively apply configuration categories from config.toml. This would allow users to manage and apply all relevant Supabase settings directly from their repository, enabling full configuration-as-code workflows. Desired Behavior • Allow toggling which configuration sections from config.toml to apply during deployment, for example: - api (API exposure, ports, schemas, TLS) - db (database settings, pooling, migrations, network restrictions) - realtime (real-time settings) - storage (file storage, bucket limits/configuration) - auth (JWT expiry, signup rules, password policies, MFA, external prov…