`auth.third_party.clerk` key ignored in config.toml

[johnny-y-wang]

Describe the bug
auth.third_party.clerk key is validated in Supabase CLI but is ignored when running supabase config push. The root cause is that supabase config push only constructs a UpdateAuthConfig object, but third-party authenticators (aka tpas) are updated via V1CreateProjectTpaIntegrationJSONRequestBody (via setting a custom OIDC issuer URL.)

This is causing configuration drift in production in addition to unable to use Clerk JWT in preview branches.

To Reproduce
Steps to reproduce the behavior:

1. Add the following block in your config.toml

[auth.third_party.clerk]
enabled = true
domain = "engaging-bear-34.clerk.accounts.dev"

2. Observe your local Supabase respects the Clerk configuration.
3. Run supabase config push
4. Observe production Supabase not aware of the updated Clerk configuration.

System information
Rerun the failing command with --create-ticket flag.

• Ticket ID: [e.g. ab1ac733e31e4f928a4d7c8402543712]
  supabase config push --create-ticket does no create a ticket.
• Version of OS: [e.g. Ubuntu 22.04]
  Not relevant.
• Version of CLI: [e.g. v1.60.0]
  2.54.11
• Version of Docker: [e.g. v25.0.3]
• Versions of services: [output from supabase services command]

Additional context
If applicable, add any other context about the problem here.

• Browser [e.g. chrome, safari]
• Version of supabase-js [e.g. v2.22.0]
• Version of Node.js [e.g. v16.20.0]