fix: Real support for .Net xUint test

[Yumitoya8569]

Current progress

The current version (1.1.3) does not work when running C# xUnit tests at all.
The reason is that the test process is not attached to the debugger.
This PR uses a workaround to attach it.

Follow-up

Currently, it uses a presumed name (testhost) to scan processes and obtain the PID.
There should be a better approach in the future.

[Yumitoya8569]

@microsoft-github-policy-service agree

[Yumitoya8569]

Update

1. Fixed an issue where the server would fail to start if the .csproj and .cs files were not in the same directory.
2. Fixed an issue where continuous requests from the agent would cause the server to crash.

Follow-up

Continuous requests cause the server to crash due to the transport implementation.
Additionally, the singleton stateless mode described in the StreamableHTTPServerTransport doc does not actually work.
So for now, just fixed it with a workaround.
There should be a better approach in the future.

[JohnGalt1717]

It would be nice if it just worked for all tests in the vs code test harness to be able to debug a given tests. It shouldn't care about which test framework is used.

Does this work?

[Yumitoya8569]

It would be nice if it just worked for all tests in the vs code test harness to be able to debug a given tests. It shouldn't care about which test framework is used.

Does this work?

Basically, it runs based on dotnet test, so it shouldn't be bound to any test framework, but I haven't tested it on other test frameworks yet.

[JohnGalt1717]

Great! Is there a way to get the AI to know to use the actual test harness so the tests show in realtime instead of kicking it off out of band? (or does it already do that with what you're doing?)

[Yumitoya8569]

Great! Is there a way to get the AI to know to use the actual test harness so the tests show in realtime instead of kicking it off out of band? (or does it already do that with what you're doing?)

This is unrelated to whether the AI knows the test framework or not.
It works just like the other parts of the project.
This PR only fixes the issue where dotnet test was not working.
If your test framework is supported by dotnet test and the C# Dev Kit extension, it should work.