feat(vscode-extension) error reporting, qol

[alii]

What does this PR do?

A few goodies implemented into the VSCode extension.

• A basic test runner that uses the TypeScript AST for finding tests. Most of this came from feat(vscode-extension): test support #13668
• Bring in the LifecycleAgent & co from Introduce InspectorLifecycleAgent and InspectorTestReporterAgent #15194
• Show errors inside of VSCode as they happen at runtime
• Implements a new DebugAdapter for communicating via a node:net Socket

How did you verify your code works?

Ran extension and tested each feature

Notes:

• Async stack traces are NOT supported. This is because JSC does not actually record them unless the debugger is open. The debugger is big overhead, so it's not open in this case.
• Ideally we would show the function name of .relatedInformation for each diagnostic. Right now we just show the error message again. This isn't amazing...
• Disabling this right now would be done by setting the BUN_INSPECT_NOTIFY variable to ''. A use case for disabling would be like when running a benchmark file (where this would actually have a very very slight performance overhead)
• The socket framer on the extension side could be rewritten

[dylan-conway]

In the future, I think we can get the function name from frame here

[alii]

Interesting, we'd need to add this to the inspector event. Probably can't guarantee that we'll always have it (@Jarred-Sumner ?)

[alii]

cc @Jarred-Sumner @dylan-conway

Could this actually be relevant? Or expected that some/certain tests are failing here

[dylan-conway]

Yup, this is a new test failure, looking into it. I believe the cause is from https://github.com/oven-sh/bun/pull/15261/files#diff-36302f74ed5420c7bee6a5460115be29fd82720720381c0d2c8bb7c934e69591L382

[alii]

This code (or at least something similar iirc) was removed previously, I think because it was printing errors twice. Did you test this locally and if so does it seem to be working? I can try it out as well to test