CLI does not support Google SSO — no way to authenticate or recover access for SSO-only accounts

The HyperDX CLI currently requires email + password authentication. For accounts created via Google SSO, there is no password to authenticate with, and no forgot-password flow works for these accounts (there's no local email+password identity to reset).

This leaves Google SSO users unable to use the CLI at all, and unable to self-recover if they need password-based access as a fallback.

Related: #369 proposes a CLI-based "break glass" password reset for accounts that have lost credentials — the same underlying gap (no credential-recovery path for SSO-created accounts) blocks CLI usage entirely for Google SSO users. Solving CLI auth for SSO accounts and #369's reset flow are closely related and may share a solution (e.g., token-based CLI auth that doesn't require email+password).

Request: support Google SSO authentication in the CLI (e.g. OAuth device-code flow or API-token-based login), so accounts created via SSO aren't locked out of CLI usage.

Start by tracing the CLI's current email + password authentication flow and compare it with the account and identity behavior described for Google SSO. Review related issue #369 for the shared credential-recovery context, then define a supported OAuth device-code or API-token login path and verify that Google SSO-created accounts can authenticate to the CLI.