Error reporting should be smoother

[isidorn]

Testing #17040

1. Have some error in your test file
2. Notice the error

I see the following problems:

1. We are piggy backing on the test infrastructure and vscode thinks this is just another test directory. Which is incorrect, thus the hover information is off and VS Code offers commands to Run All tests
2. Clicking on the error does not take you to Python / Output
3. Should we introduce some infrastructure for error reporting, or do we maybe already have something @connor4312

[connor4312]

The markdown supports command links, could that be used to show error details here?

[karthiknadig]

If you hover on that item you should see the full error details. But I think if we can get a output channel (just like for runs) to report discovery issues that would be great. Since there is already a "Show Output", I think having a way to add discovery errors to that should help with reporting these. /cc @connor4312

Previously we had a custom logging channel that captured both the discovery and run output. Now those two are separated, because there is a way to capture run output for each run.

[connor4312]

It seems like the error is pretty large and textual, maybe it should be written and opened in the editor from a temp file (or custom TextDocumentContentProvider)?

[karthiknadig]

If users close it accidentally, that error will be lost right? I feel like it needs to be in the logs. Just need to isolate it from the rest of the python logs. Otherwise it might be to difficult to find the issue.

/cc @luabud

[eleanorjboyd]

we have completed item 2, there is a potential Connor and I might discuss better error reporting but I think for now im going to close this issue since it is stale (pre python testing rewrite), and will move to the updated conversation happening here: #22154