Split out detector types into separate proto file in order to narrow CODEOWNERS scope

[casey-tran]

Description:

We want to move the detector types out of the Scanning team purview. So I split off detector types into its own proto file (so that file detector_type.proto can be owned by the Integrations team), regenerated the pb files with "make protos", and made the detector files use the new generated detector_type.pb.go. Included the new detector_type.proto file in CODEOWNERS and made CODEOWNERS categories that contain larger teams be towards the top so that more fine grained ownership is filtered properly.

Checklist:

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

---

Note

Medium Risk
Wide mechanical refactor across many detectors/config paths; risk is mainly build/runtime incompatibilities if any code still depends on the old detectorspb.DetectorType definitions or enum numbering.

Overview
Splits detector type definitions into a dedicated proto. DetectorType is moved into proto/detector_type.proto (with regenerated Go bindings under pkg/pb/detector_typepb).

Updates references and ownership. Call sites across config, custom detectors, and many detector implementations/tests are switched from detectorspb.DetectorType to detector_typepb.DetectorType, internal docs are updated to point at the new proto, and CODEOWNERS is reordered/adjusted to assign proto/detector_type.proto specifically to Integrations while keeping broader proto/ ownership shared.

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

[shahzadhaider1]

Looks good. But I think there might be some stale references created by this. For example: hack/docs/Adding_Detectors_external.md

[casey-tran]

Looks good. But I think there might be some stale references created by this. For example: hack/docs/Adding_Detectors_external.md

Thanks for the catch Shahzad. I went ahead and updated the docs.