fix(cli): read Go Windows credentials via findCredentials

[Versa-Sync-Studios]

Fixes #5415.

The Windows fallback added for Go-written credentials used Entry.withTarget(...).getPassword().

On Windows, that does not read the Go-shaped target credential correctly. findCredentials(service, target) can read it, so this uses that path for the Go Windows target while preserving the existing default keyring and file fallback behavior.

The legacy credentials unit test now covers the target lookup path.

Tested with:

npx bun run .\node_modules\vitest\vitest.mjs run src/legacy/auth/legacy-credentials.layer.unit.test.ts --config vitest.config.ts

[jgoux]

Thanks for your contribution! I added small changes, can you confirm it works before merging?

[Versa-Sync-Studios]

Tested the updated branch on local Windows and on a clean windows-latest GitHub Actions runner.

I used supabase@2.102.0 login --token to write a Go keyring credential under the supabase-staging profile, then ran the current legacy TS projects list path from this branch.

Results:

• Before writing the credential, the command fails with Access token not provided.
• After the Go-written credential exists, it no longer fails with Access token not provided.
• It also no longer fails with Invalid access token format after the latest decode commit.
• With the fake token, it reaches the expected Unauthorized response, which confirms the credential was read and decoded.

I also reran the focused unit test locally:

npx bun run .\node_modules\vitest\vitest.mjs run src/legacy/auth/legacy-credentials.layer.unit.test.ts --config vitest.config.ts

Result: 17 tests passed.

[jgoux]

Thanks for pushing this to the finish line! 🙏