Component-level debugging support (dotnet)

[EronWright]

Extends debugging support to components via RunPlugin.

[EronWright]

Here's a brief explanation for what's happening here, which is a small change to how the pre-built executable is run.

As before, the plugin builds the project before running it, to capture build output for display purposes. Then it runs the pre-built executable. Previously, we used dotnet run --no-build --project ... to do that. The dotnet run sub-command automatically locates and executes the pre-built executable (e.g. <project>/bin/Debug/net8.0/dotnet-components.dll).

The issue with that approach is that it runs the executable as a sub-process that is impractical to attach to. The new approach is to run the executable directly using dotnet <assembly-name>, which one may attach to directly and is how the Run RPC is implemented.

To use dotnet <assembly-name>, one must locate the assembly by hand. The Run code uses an awkward approach (see code), so here I'm trying a different way that is based on interrogating msbuild for information about the build outputs:

// dotnet msbuild -getProperty:OutputPath -getProperty:AssemblyName
{
  "Properties": {
    "OutputPath": "bin/Debug/net8.0/",
    "AssemblyName": "dotnet-components"
  }
}

I do think that dotnet msbuild -getProperty is a portable command; anyone disagree? (ref)