Test workflow in C#DK has problems compared to C# vanilla test workflow

The problems are all based around how C#DK runs tests vs how C# vanilla runs tests.

When I use the C#DK icon to run a test, it does a build in the terminal, then runs the test in a background window. This is pathological in a couple ways:

1. It steals my bottom pane focus from the output window (where I can actually see the test output) to a terminal window.

2. The terminal window now overlaps my existing terminal, so my terminal is now hidden too and I have to press an additional key.
   1. Except that I ran the test in the ide, so the editor has my focus, so I can't press a key, because the key goes to the editor not the terminal.
3. Errors don't appear unless I click on the failure in the test explorer pane (which was not open).
4. When I click on it, it shows an inline view of the error, but it jumps to the location of the thrown exception, which in this case is in a separate file because it's part of a helper function.

6. The inline view is actually worse than the terminal output window. Normally the terminal output window recognizes file paths and offers to jump to them on ctrl+click. The test explorer inline view doesn't have this feature, so even though the actual location of the failure is in the error message, I can't jump to it with ctrl+click.