ci: pass --coverage-settings as an absolute path

[davidnmbond]

The coverage job has failed on main since 2026-10-07 with:

Option '--coverage-settings' has invalid arguments: Provided settings file doesn't exist or is invalid.

Cause

Microsoft.Testing.Extensions.CodeCoverage was bumped 18.11.2 -> 18.12.0 by a governance remediation commit (297f75d). 18.12.0 rejects a relative --coverage-settings path (it resolves it against the test host, not the repo root) but accepts an absolute one. coverage.config itself is fine: reproduced locally, the same file is accepted by absolute path and rejected by relative path.

Change

--coverage-settings ${{ github.workspace }}/coverage.config, the form PanoramicData.NugetManagement's CoverageSettingsPathEditor produces.

Checked

Reproduced the rejection locally with 18.12.0, and confirmed the absolute path is accepted. The coverage job on this PR is the real confirmation.

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Coverage ∅ diff coverage

Metric	Results
Coverage variation	Report missing for 7d244a71
Diff coverage	✅ ∅ diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (7d244a7)	Report Missing	Report Missing	Report Missing
Head commit (b0b43a7)	206	135	65.53%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#52)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

¹ Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

No merge-blocking issues were identified. Codacy reports the PR as up to standards. The required end-to-end verification that the absolute coverage settings path is accepted and coverage is generated has not been demonstrated.

Test suggestions

• Run the CI coverage command with the absolute coverage.config path and verify that the settings file is accepted and coverage is generated.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Run the CI coverage command with the absolute coverage.config path and verify that the settings file is accepted and coverage is generated.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}