adding customizable successRanges and rotatedRanges to customDetector

[jordanTunstill]

Description:

This would allow users to add successRanges and rotatedRanges to their customDetectors, for verification purposes, allowing them control/configuration over what is considered live/rotated for these custom detections.

Checklist:

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

---

Note

Medium Risk
Changes custom detector verification semantics based on HTTP status codes and adds a new proto field, which could affect how secrets are marked verified/unverified and how verification errors are reported.

Overview
Custom detector webhook verification now supports configurable HTTP status success and rotated code ranges via successRanges and the new rotatedRanges, allowing verifiers to mark secrets as live, rotated, or inconclusive based on status codes (while keeping legacy behavior when neither is provided).

This adds range matching/validation utilities, updates NewWebhookCustomRegex to validate both range sets, records truncated verifier responses on “live” outcomes, and introduces tests covering YAML parsing, range validation/matching, mixed legacy+ranged verifier behavior, and verification error handling when responses match neither configured set.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

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

^{Reviewed by Cursor Bugbot for commit be9bfc5. Configure here.}