This change primarly adds a new `Open with...` entry to the explorer context menu. To do this however, I had to make a few other changes:

- Add a new explorer context key for availible editors
- Moved the editor select prompt into a new function called `openEditorWith`
- Use `openEditorWith` for the new `open with` explorer command as well as for the `reopen with` command

For #95852

Fixes #95909

Notebook integration test and undo/redo

https://github.com/microsoft/vscode/issues/95996

fixes #95993

Fixes #95919

Fix inconsistent 'when' clause for toggle case view
Fix #95618

Make terminal echo integration test more reliable

* debug: enable js-debug to auto attach

This modifies the debug-auto-launch extension to trigger js-debug as
outlined in https://github.com/microsoft/vscode/issues/88599#issuecomment-617242405

Since we now have four states, I moved the previous combinational logic
to a `transitions` map, which is more clear and reliable. The state
changes are also now a queue (in the form of a promise chain) which
should avoid race conditions.

There's some subtlety around how we cached the "ipcAddress" and know
that environment variables are set. The core desire is being able to
send a command to js-debug to set the environment variables only if they
haven't previously been set--otherwise, reused
the cached ones and the address.

This process (in `getIpcAddress`) would be vastly simpler if extensions
could read the environment variables that others provide, though there
may be security considerations since secrets are sometimes stashed
(though I could technically implement this today by manually creating
and terminal and running the appropriate `echo $FOO` command).

This seems to work fairly well in my testing. Fixes #88599.

* fix typo

* clear js-debug environment variables when disabling auto attach

fixes #94285
Co-authored-by: NAlex Ross <alros@microsoft.com>

Fixes #95945

Part of #95945

Fixes #95966

Fixes #95966

Adopt `vscode-oniguruma-wasm`

Some vars were conditionally resolved by first checking `folderUri`.
This is wrong, as `getFolderUri()` may return a valid one even when
`folderUri` is undefined (when `argument` is used).

fixes #95482
Co-authored-by: NAlex Ross <alros@microsoft.com>