Docs: Supabase secret sync — behavior when hitting Supabase's hardcoded 100-secret limit is undocumented

Path: /integrations/secret-syncs/supabase (https://infisical.com/docs/integrations/secret-syncs/supabase)

Supabase enforces a hard limit of **100 secrets per project**, which is hardcoded on their side and cannot be raised. The Supabase secret sync docs don't describe what happens when this limit comes into play.

Could you clarify (and ideally document) the behavior for these cases:

1. **Syncing more than 100 secrets**: If the Infisical source path contains more than 100 secrets, what does the sync do? Fail outright, sync the first 100 and drop the rest, or something else?
2. **Target already at the cap**: If the Supabase project is already at 100 secrets (including secrets not managed by Infisical), how does the sync handle new additions — hard error, partial write, retry loop?
3. **Error surfacing**: Where does this failure show up (sync status in the UI, logs, webhook/alert)? Is it distinguishable from other sync errors?
4. **Overwrite vs. import modes**: Does the behavior differ depending on the configured sync mode (e.g. overwriting destination secrets vs. importing existing ones)?

We're running against this exact limit in production, so understanding the failure mode matters for us before relying on the sync. Thanks!

Start with the Supabase secret-sync documentation at /integrations/secret-syncs/supabase. Verify the behavior for exceeding 100 secrets, a target already at the cap, error surfacing, and overwrite versus import modes; done means the documented page answers each case accurately.

Written by the indexing model from the issue text.