Fix coverage settings path and trait filter

[westey-m]

Motivation and Context

Description

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines
• All unit tests pass, and I have added new tests where possible
• Is this a breaking change? If yes, add "[BREAKING]" prefix to the title of the PR.

[Copilot]

Pull request overview

Updates the .NET CI workflow to make code coverage settings path resolution more robust and to adjust how integration tests are filtered/excluded during dotnet test runs.

Changes:

• Build an explicit path for tests/coverage.runsettings and pass it to --coverage-settings.
• Modify the integration test selection/exclusion to use a single --filter-query expression.

[Copilot]

--filter-query is a name-based selector (assembly/namespace/class/method). Appending [Category!=IntegrationDisabled] doesn’t appear to be a supported syntax in this repo’s documented MTP usage, and it risks selecting 0 tests and returning exit code 8 (which we ignore), effectively skipping all integration tests. Keep the trait exclusion as a separate argument (e.g., restore --filter-not-trait "Category=IntegrationDisabled") or use a verified MTP-supported trait filtering flag/syntax.

Suggested change

	--filter-query "/*IntegrationTests*/*/*/*[Category!=IntegrationDisabled]"
	--filter-query "/*IntegrationTests*/*/*/*" `
	--filter-not-trait "Category=IntegrationDisabled"