[release/9.4] Backport a fix to add .dotnet to PATH on windows

[radical]

This was originally a part of #9868, and the fix stands on its own.

---

Try setting the PATH in a os-aware way

(cherry picked from commit 08a4b70)

cc @joperezr @captainsafia

Customer Impact

Testing

Risk

Regression?

[Copilot]

Pull Request Overview

This PR backports a fix to ensure that the .dotnet directory is properly added to the PATH environment variable on Windows systems in the GitHub Actions workflow. The change addresses a platform-specific issue where the dotnet runtime wasn't being correctly resolved during test execution.

Key changes:

• Adds .dotnet directory to PATH for both Linux/macOS and Windows environments
• Ensures tests consistently use the restored dotnet runtime rather than system dotnet
• Uses OS-appropriate PATH variable syntax ($GITHUB_PATH vs $env:GITHUB_PATH)

[joperezr]

Probably a dump question, but why not just root's dotnet.cmd? It is exactly for that purpose after all.

[captainsafia]

Probably a dump question, but why not just root's dotnet.cmd? It is exactly for that purpose after all.

The issue I was running into was scenarios where we launched dotnet from Aspire code, in my case via the dotnet publish call in the ResourceContainerImageBuilder. We need to propagate the PATH to those callers as well.

[joperezr]

Probably a dump question, but why not just root's dotnet.cmd? It is exactly for that purpose after all.

The issue I was running into was scenarios where we launched dotnet from Aspire code, in my case via the dotnet publish call in the ResourceContainerImageBuilder. We need to propagate the PATH to those callers as well.

ahh, that makes sense. Thanks for clarifying.