Add Antigravity OAuth support with manual token and local import

[validatedev]

Summary

This pull request adds support for managing Antigravity provider accounts, including OAuth and manual token entry, in the Providers preferences pane. It introduces new UI options for adding, importing, and managing Antigravity credentials, updates the provider descriptor logic, and refines the token account entry experience for providers that require multiple fields. Additionally, it includes dependency and CI updates to support these features.

Antigravity Provider Account Management:

• Added support for Antigravity accounts in the Providers preferences pane, including segmented manual entry (access token and optional refresh token), Google OAuth sign-in, and importing credentials from the Antigravity app database. The UI dynamically adapts based on provider and system configuration. [1] [2] [3] [4]
• Implemented error handling and user feedback for credential import, including alerts for missing credentials, database not found, and full disk access requirements.

UI/UX Improvements:

• Refined the token account entry row to support two-field entry for providers like Antigravity, and adjusted the layout and controls for better usability. [1] [2]
• Added "Antigravity" to the provider picker in the debug pane for log viewing.

Dependency and Build Updates:

• Added swift-protobuf as a package dependency and linked it to the main target. [1] [2]
• Updated CI workflow to install SQLite3, required for reading the Antigravity database.

Security and Configuration:

• Added a .gitguardian.yml configuration to ignore known public Antigravity OAuth credentials, preventing false positives in secret scanning.

Screenshot

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[validatedev]

For GitGuardian fail, I cannot do anything as these are the keys which are used by Antigravity itself.

[validatedev]

@steipete when you have time you can review the PR, it’s functionally complete. There are some existing linting errors in CI across the whole repo, so I preferred not to touch those in this PR.

[validatedev]

Saw some edge case bug, fixing it. Until then it is draft