Renamed AnypointOAuth2 detector's AnalysisInfo keys to make it consistent with its Analyzer

[MuneebUllahKhan222]

Description:

This PR fixes a mismatch between the AnypointOAuth2 detector and its corresponding analyzer.

Previously, the detector populated credential fields as id and secret, while the analyzer expects them to be provided as client_id and client_secret. This inconsistency caused the analyzer to fail when processing detected credentials.

Checklist:

• Tests passing (make test-community)?
• Lint passing (make lint this requires golangci-lint)?

---

Note

Low Risk
Small, localized changes to detector result metadata; no changes to matching/verification behavior beyond adding extra output fields.

Overview
Fixes verified-result metadata emitted by the AnypointOAuth2 detector by renaming AnalysisInfo keys from id/secret to client_id/client_secret so downstream analyzers receive the expected fields.

Also updates the Coinbase detector to (a) populate AnalysisInfo with key_name and key on successful verification and (b) includes a minor formatting fix in isValidECPrivateKey.

^{Reviewed by Cursor Bugbot for commit 3dd0f29. Bugbot is set up for automated code reviews on this repo. Configure here.}

[shahzadhaider1]

While we are at it, could we also populate the AnalysisInfo in the following detector:

1. pkg/detectors/coinbase/coinbase.go

[unsmith]

Approved on behalf of product-eng.