Promote uv.lock to stable

[Ryan Brandenburg (ryanbrandenburg)]

The telemetry for this detector is looking good so let's promote it from experimental to stable. This will turn it on-by-default and increase the # of components that are detected in any repository that uses uv by default.

[Copilot]

Pull request overview

Promotes the UvLockComponentDetector from experimental to stable by removing its experiment-based rollout and marking it as a non-experimental detector, making it enabled by default in the orchestrator.

Changes:

• Removed the UvLockDetectorExperiment configuration and its orchestrator test coverage.
• Updated UvLockComponentDetector to no longer implement IExperimentalDetector, and adjusted detector registration tests accordingly.
• Updated detector documentation to reflect stable status (and minor formatting cleanup).

Show a summary per file

File	Description
test/Microsoft.ComponentDetection.Orchestrator.Tests/Experiments/UvLockDetectorExperimentTests.cs	Removes tests for the uv experiment configuration since the experiment is being retired.
test/Microsoft.ComponentDetection.Detectors.Tests/ComponentDetectorTests.cs	Updates assertion to ensure UvLockComponentDetector is not experimental.
src/Microsoft.ComponentDetection.Orchestrator/Extensions/ServiceCollectionExtensions.cs	Removes DI registration for the uv experiment configuration.
src/Microsoft.ComponentDetection.Orchestrator/Experiments/Configs/UvLockDetectorExperiment.cs	Removes the uv experiment configuration implementation.
src/Microsoft.ComponentDetection.Detectors/uv/UvLockComponentDetector.cs	Drops IExperimentalDetector implementation to make the detector stable/on-by-default.
docs/detectors/uv.md	Minor formatting change in the uv detector docs.
docs/detectors/README.md	Updates the uv detector status from Experimental to Stable.

Review details

• Files reviewed: 7/7 changed files
• Comments generated: 0
• Review effort level: Lite

[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 🙂