feat: implement export filter functionality for resource exports

[Gijs Reijn (Gijsreyn)]

PR Summary

Adds engine-side post-filtering for export via a new exportFilter resource directive.

PR Context

Fixes #1486.

[Copilot]

Pull request overview

Implements engine-side post-filtering for dsc config export results via a new exportFilter resource directive, enabling consistent wildcard/equality filtering even for resources that don’t implement native export filtering.

Changes:

• Adds exportFilter to the configuration resource directives schema and applies it in the export pipeline after resource.export(...).
• Introduces configure::export_filter matching logic (case-insensitive * wildcard for strings; OR across filter objects, AND within each object) plus unit tests.
• Adds Pester coverage for exportFilter behavior and updates the dsctest export resource to emit a name property for filtering.

Reviewed changes

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

Show a summary per file

File	Description
tools/dsctest/src/main.rs	Emits per-instance name values to enable filter-driven tests.
tools/dsctest/src/export.rs	Extends the test export payload schema with optional name.
lib/dsc-lib/src/dscresources/command_resource.rs	Adjusts when “export filtering not supported” is raised (only for non-empty input).
lib/dsc-lib/src/configure/mod.rs	Wires exportFilter from directives into the export pipeline.
lib/dsc-lib/src/configure/export_filter.rs	Adds the engine-side filtering implementation + Rust unit tests.
lib/dsc-lib/src/configure/config_doc.rs	Adds export_filter directive field to the config document model/schema.
lib/dsc-lib/locales/en-us.toml	Adds localized message for filter reduction logging.
dsc/tests/dsc_export.tests.ps1	Adds integration tests validating exportFilter behavior across scenarios.
dsc/src/resource_command.rs	Updates call site for the changed export helper function signature.

[Steve Lee (SteveL-MSFT)]

Changes look fine, but can you remove the wildcard filtering support in the service, firewall, and dism resources? I would expect all the tests to still pass (assuming they don't call the resource exe directly, if so, they would need to be udpated to go through dsc).

[Gijs Reijn (Gijsreyn)]

Steve Lee (@SteveL-MSFT) - good catch, but it had some caveats. I've replaced them with tests that append * to a known valid identifier. Exact-match and existing AND/OR filtering coverage remained in place.

[Copilot]

Pull request overview

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

[Steve Lee (SteveL-MSFT)]

Gijs Reijn (@Gijsreyn) you have a test failure and can you see if you can improve the code coverage?

[Gijs Reijn (Gijsreyn)]

Steve Lee (@SteveL-MSFT) - I'm a bit surprised by the coverage report. The previous run was 41%, and after adding more tests, it dropped to 21% in the latest one.

[Steve Lee (SteveL-MSFT)]

Gijs Reijn (@Gijsreyn) let me look into the CC report, I think the problem is that deleted lines is being calculated wrong as not covered

[Steve Lee (SteveL-MSFT)]

WG discussed this:

• remove the exportFilter directive
• emit INFO message when engine filter is applied
• the INFO message should indicate this feature as Experimental

[Gijs Reijn (Gijsreyn)]

Steve Lee (@SteveL-MSFT) - made the adjustments. Let me know if this is solid.

[Copilot]

Pull request overview

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

Comments suppressed due to low confidence (1)

resources/dism_dsc/optionalfeature.dsc.resource.json:104

• The schema text for description says it is "Returned by the get operation", but optional_feature::handle_export() now exports full feature info (via get_feature_info()), which likely includes description. The schema should reflect what export actually returns.

                            "description": {
                                "type": "string",
                                "title": "Description",
                                "description": "The description of the optional feature. Returned by the get operation."
                            },

[Steve Lee (SteveL-MSFT)]

Sorry, just occurred to me looking over the latest change that the dism resource manifests need to declare they explicitly support filtering. Although for backwards compat it doesn't need to, we want those resource manifests to represent best practice.

[Gijs Reijn (Gijsreyn)]

Sorry, just occurred to me looking over the latest change that the dism resource manifests need to declare they explicitly support filtering. Although for backwards compat it doesn't need to, we want those resource manifests to represent best practice.

Done! And also bumped up the version number for good measure.