fix(ui): prevent silent overwrite of existing API key connections on …

[dilneiss]

…re-add

When adding a second API key for the same provider, the backend uses a name-based upsert. Since all new connections defaulted to the name "main", the second key would silently overwrite the first one with no warning to the user.

Changes:

• Add existingConnectionCount prop threaded from ProviderDetailPageClient through ProviderModalsPanel into AddApiKeyModal
• Compute a unique default connection name based on existing count to prevent name collision: first connection defaults to "main" (backward compatible), subsequent ones get a numeric suffix ("main-2", "main-3", ...)
• Properly reset entire form state on modal open (not just baseUrl) to avoid stale field values leaking across opens

Fixes silent data loss when managing multiple API keys for the same provider.

Summary

• Describe the user-facing or operational change.

Related Issues

• Closes #
• Related to #

Validation

• npm run lint
• npm run test:unit
• npm run test:coverage
• Coverage is still >= 60% for statements, lines, functions, and branches
• SonarQube PR analysis is green or any remaining issues are explicitly documented below

Tests Added Or Updated

• List every changed or added automated test file.
• If no production code changed, state that here.

Coverage Notes

• If this PR changes src/, open-sse/, electron/, or bin/, explain which tests cover the change.
• If coverage moved down in any touched file, explain why and what follow-up task will recover it.

Reviewer Notes

• Call out any risky areas, migrations, feature flags, or manual validation that reviewers should know about.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[diegosouzapw]

Merged — thank you, @dilneiss! Synced onto release/v3.8.46 with two small adjustments: (1) the pure default-name derivation was extracted to computeConnectionDefaultName.ts and covered by a unit test (main → main-2 → main-3, undefined/negative → main) to satisfy the test gate for UI-only logic; (2) the on-open form reset was kept as a spread ({ ...current, name, baseUrl }) rather than a full field-by-field literal — the literal predated #6351 and would have dropped the new GLM team-quota fields on reopen, and the spread also keeps the frozen modal's growth to +7. Behavior is unchanged: a second key for the same provider gets a unique name so the backend name-based upsert can't overwrite the first connection.