Promote the DockerCompose, Dockerfile, and Helm detectors to default on.

[jpinz]

This pull request removes the "experimental" status from three component detectors: Docker Compose, Dockerfile, and Helm. The detectors are now considered stable, and their outputs are included in scan results by default, without requiring special command-line arguments. Documentation has been updated to reflect this change, and the IExperimentalDetector interface has been removed from the relevant classes.

Detector status changes:

• Removed the IExperimentalDetector interface from DockerComposeComponentDetector, DockerfileComponentDetector, and HelmComponentDetector, making them standard detectors. [1] [2] [3]

Documentation updates:

• Updated docs/detectors/dockercompose.md to remove references to experimental status and the need for --DetectorArgs DockerCompose=Enable. [1] [2]
• Updated docs/detectors/dockerfile.md to remove references to experimental status and the need for --DetectorArgs DockerReference=Enable. [1] [2]
• Updated docs/detectors/helm.md to remove references to experimental status and the need for --DetectorArgs Helm=Enable. [1] [2]

These changes mean that users will now see Docker Compose, Dockerfile, and Helm detection results in their scans by default, improving usability and reducing configuration complexity.

[github-actions]

👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:

• The detector detects more or fewer components than before
• The detector generates different parent/child graph relationships than before
• The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂

[Copilot]

Pull request overview

This pull request promotes the Docker Compose, Dockerfile, and Helm detectors from “experimental” to standard detectors so their detected components are included in scan results by default. This aligns with the orchestrator’s existing behavior where IExperimentalDetector implementations are excluded from results unless explicitly enabled.

Changes:

• Removed IExperimentalDetector from DockerComposeComponentDetector, DockerfileComponentDetector, and HelmComponentDetector so their outputs are included in scan results by default.
• Updated detector documentation pages to remove “experimental” messaging and opt-in --DetectorArgs ...=Enable instructions.

Show a summary per file

File	Description
src/Microsoft.ComponentDetection.Detectors/dockercompose/DockerComposeComponentDetector.cs	Stops treating Docker Compose detection as experimental by removing IExperimentalDetector.
src/Microsoft.ComponentDetection.Detectors/dockerfile/DockerfileComponentDetector.cs	Stops treating Dockerfile image reference detection as experimental by removing IExperimentalDetector.
src/Microsoft.ComponentDetection.Detectors/helm/HelmComponentDetector.cs	Stops treating Helm values image reference detection as experimental by removing IExperimentalDetector.
docs/detectors/dockercompose.md	Removes experimental/opt-in wording now that results are included by default.
docs/detectors/dockerfile.md	Removes experimental/opt-in wording now that results are included by default.
docs/detectors/helm.md	Removes experimental/opt-in wording now that results are included by default.

Copilot's findings

• Files reviewed: 6/6 changed files
• Comments generated: 0

[jpinz]

This PR is on hold until #1819 is merged and deployed. With validation that the timeouts for the helm detector has gone down.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.0%. Comparing base (248e744) to head (329dc3d).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@     Coverage Diff      @@
##   main   #1818   +/-   ##
============================
============================

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.