Fix release.yml Test step hanging by specifying target frameworks

[Copilot]

The release workflow's Test step hangs indefinitely because dotnet test runs without a --framework flag on a multi-targeted project (net8.0;net9.0).

Changes

• Split single Test step into two framework-specific steps with explicit --framework flags
• Matches the approach used in the working dotnet-test.yml workflow

# Before
- name: Test
  run: dotnet test --configuration Release --no-restore --no-build --verbosity normal

# After  
- name: Test net8.0
  run: dotnet test --configuration Release --no-restore --no-build --verbosity normal --framework net8.0

- name: Test net9.0
  run: dotnet test --configuration Release --no-restore --no-build --verbosity normal --framework net9.0

Original prompt

the release.yml workflow never ends, during the Test step, while the dotnet-test.yml does not. I think thats because dotnet test is not executed with a target framework. Is it possible to change this workflow to run tests like in dotnet-test.yml ?

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.