Use `conda run` in the debug adapter

[DonJayamanne]

Suggestion from Conda team

[DonJayamanne]

conda run <env name> python <xyz.py>

The issue comes from spike #5664

[karrtikr]

Prescribed solution

• communicate to the (old) debug adapter the path to conda
• use "conda run" in the (old) debug adapter
  • see https://github.com/Microsoft/vscode-python/blob/85ea1b546bf0461dd019270de24fbbe4ac2f335a/src/client/debugger/debugAdapter/DebugClients/LocalDebugClient.ts#L149
• do not "auto activate" if it's the debug adapter terminal
  • see https://github.com/Microsoft/vscode-python/blob/86d669e3906c533bb6f674b1745ce90389b8e75a/src/client/terminals/activation.ts
  • when the name is equal to 'Python Debug Console' (if not, research some other means by which we can identify if it is the 'Python Debug Console'), we do not send the activation commands.

questions:

• how to communicate the conda path to the debug adapter? See option 2 in Spike - Activation script sent to terminal after debugger starts (Use Conda run) #5664 (comment).
• use "conda run" elsewhere in the extension? (only needed in cases where we need to run a command and can only send one; e.g. debug adapter)

[ericsnowcurrently]

FYI, all other env types are fine because using the python executable directly is equivalent to activating first. Conda doesn't work like that and requires activation.

Also, keep in mind that the key objective of this issue is to resolve the race condition in env activation when we launch the debugger.

[DonJayamanne]

Partial PR #6959