{assembly} or {framework} options to the logger don't work with .NET 10

## Describe the bug

With .NET 10 installed

`dotnet test --logger \"nunit;LogFilePath=\"{assembly}\"-\"{framework}\"-test-output.xml\"`

produce an error MSB4177: Invalid property. The name "{assembly}-{framework}-test-output.xml" contains an invalid character "{".

## Steps To Reproduce

Call

`dotnet test --logger \"nunit;LogFilePath=\"{assembly}\"-\"{framework}\"-test-output.xml\"`

like described in [NUnit Test Logger](https://github.com/spekt/nunit.testlogger)

## Expected behavior

It works like in .NET 8

## Actual behavior

error MSB4177

----

Reported by @JoergHoffmannMeVis in https://github.com/microsoft/testfx/issues/7141

Start by reproducing the reported `dotnet test --logger "nunit;LogFilePath="{assembly}"-"{framework}"-test-output.xml"` command with .NET 10 and compare it with .NET 8. Trace the dotnet test logger argument handling and the NUnit Test Logger behavior; done means the documented command works without MSB4177 and produces the expected assembly- and framework-named output file.

Written by the indexing model from the issue text.