Provide better details for `Debug: Toggle Auto Attach`

[jsoref]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

macOS 12.6
VSCode Version: 1.71.1 (Universal)
JavaScript Debugger v1.71.0

jsoref@jsoref-mbp yarn % which node
/Users/jsoref/.nvm/versions/node/v16.13.2/bin/node

This appears to be a node and it appears to be in my path.

When I use cmd-shift-p and enter Debug: Toggle Auto Attach and toggle to something that isn't Disabled, I get this dialog:

Clicking details takes me to #708

There are three things you can do to get around this issue:

1. Update to a Node version >12
2. If the error is not correct (which may happen when using .rc-file based version managers like nvm or nvs), you can still enable auto attach by running the command Debug: Force Enable Auto-Attach from the command palette. If this breaks your setup, you can restore your state by setting auto attach to disabled and then reloading the VS Code window.
3. You can use the previous version of auto attach by turning the setting debug.javascript.usePreviewAutoAttach off

I tried 3 and that didn't seem to do anything.

Describe the feature you'd like
A clear and concise description of what you want to happen.

I'd like a sheet or pane or something that actually helps a user figure out how to make things work, or a page that has current information.

[connor4312]

Now that Node 12 is EOL and its usage is continuing to decrease in VS Code, I think we can loosen the restriction to allow turning auto attach on with spaces in the path.

[alexr00]

@connor4312 what's the best way to verify this?