fix: Short-circuit adapter discovery when a native resource type has no matching version

[Gijsreyn]

PR Summary

This pull request makes discovery fail fast in a scenario when a configuration document pins a resource with requireVersion, and the requested type is a known native command-based DSC resource, but no installed version satisfies the requirement.

When a user adds the requireAdapter in the configuration document, a sweep still runs, so that behavior is unchanged. It is mainly on native type + version mismatch + no requireAdapter.

PR Context

Fixes #1531

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Optimizes command-based resource discovery by avoiding adapter enumeration in cases where remaining unsatisfied filters correspond to natively-registered resource types (and no adapter is explicitly required), and adds trace logging + test coverage for the new behavior.

Changes:

• Add pre-filtering step to only perform adapter discovery for filters that actually require it.
• Add a trace message when adapter discovery is skipped for a natively-registered type due to version mismatch.
• Add a PowerShell test ensuring adapter discovery is skipped in the native-type version mismatch case.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
lib/dsc-lib/src/discovery/command_discovery.rs	Introduces adapter candidate filtering and early-return to skip adapter discovery in native-type mismatch scenarios.
lib/dsc-lib/locales/en-us.toml	Adds localized trace message for the adapter-skip scenario.
dsc/tests/dsc_config_version.tests.ps1	Adds regression test asserting adapter discovery is not invoked when native type version constraints can’t be met.