[INS-339] Add New Relic User Key detector

[mustansir14]

Description:

This PR adds the New Relic User Key Detector.

Regex: \b(NRAK-[A-Z0-9]{27})\b

Verification:
For verification, we use the New relic NerdGraph API: https://api.newrelic.com/graphql.
We send a POST request with body { requestContext { userId } }. A response code of 200 means the key is valid. 401 means it is an invalid/rotated key and 403 means the region is incorrect.
Note: For EU region keys, the endpoint should be https://api.eu.newrelic.com/graphql"

Corpora Test:
The detector does not appear in the list.

Checklist:

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

---

Note

Medium Risk
Adds a new detector that introduces outbound verification requests to New Relic’s NerdGraph API (US/EU), which could impact scan performance/behavior if the endpoint is slow or changes responses. Otherwise changes are additive and isolated to detector registration and protobuf enum wiring.

Overview
Adds a new NewRelicUserKey detector that finds NRAK-... user API keys via regex and optionally verifies them by calling New Relic’s NerdGraph GraphQL endpoint (trying US and EU regions) and recording region/user_id in ExtraData.

Registers the detector in the default detector list and extends the detector type enum (proto/detectors.proto + generated detectors.pb.go). Includes unit, integration, and benchmark tests for matching and verification behavior.

^{Written by Cursor Bugbot for commit 849426f. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}