[INS-254] Datadog detector verification fix and endpoint configuration

[MuneebUllahKhan222]

Description:

Datadog token verification previously relied on an App-key–dependent endpoint (/api/v2/users) to validate the Application Key + API Key combination. If this endpoint returned an error (for example, due to insufficient App Key permissions), the detector would mark the token as unverified and skip API key validation entirely.
Additionally, Datadog uses region-specific API endpoints. When the hard-coded cloud endpoint did not match the user’s actual region, verification requests were sent to the wrong endpoint.

This behaviour caused valid Datadog API keys to be reported as unverified, resulting in false negatives.

To resolve this issue I have done the following changes:

• Removed API key validation from this detector and introduced a dedicated API key detector here

• Added support for user-provided Datadog endpoints.

  • If no endpoint is explicitly provided, the detector attempts to infer it from the data using regex.
  • If inference fails, it falls back to the default cloud endpoint hard-coded in the codebase.

Checklist:

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

[kashifkhan0771]

Good work 🚀

[nabeelalam]

Looks good! Thanks!