[24068] Remove Legacy -- behavior and use of UnparsedTokens

[Tunduk]

@baronfel Hi! I messed up with branches a little, so here is a new PR. Sorry for this, I'll be more careful in next time.
Link for history

[Tunduk]

@baronfel
Could you help me, please? On my local PC Microsoft.DotNet.Tools.Tool.Install is passed ok but in CI there are errors.
Am I doing something wrong?

[baronfel]

@Tunduk looks like flakiness on those tests in the CI environment. I've seen the same recently. I restarted the 2 failed runs.

[baronfel]

Alright! @marcpopMSFT this is good to merge, I've done all the local testing I was concerned about.

[marcpopMSFT]

@baronfel can you click the approve button so when I merge and everything breaks, I have a paper trail back to you? :P

[marcpopMSFT]

Thank you for your contribution!

[baronfel]

And thank you for sticking with it @Tunduk!

[baronfel]

@Tunduk it looks like this may have regressed dotnet test a bit (see the linked microsoft/vstest issue). I'm going to dig into it a bit today and see if I can determine the cause.

[nagilson]

This is the first time I've seen @marcpopMSFT use :P and I am very intrigued. More importantly, I don't see the issue attached in reference to this:

see the linked microsoft/vstest issue

Was it this? microsoft/vstest#4014