[meta] Use `conda run` for running tools

[luabud]

[luabud]

• changes in PythonExecutionFactory and PythonExecutionService fix the following (Update PythonExecutionService to support "conda run". #7696):
  • formatting
  • linting
  • testing (partial)
  • installers (partial)
  • debugger (partial)
  • interpreter discovery (partial)
  • import sorting (partial)
  • jedi
  • refactoring
  • (datascience?)
• currently do exec() (Stop using "exec()" in the extension. #7697):
  • testing (partial)
  • installers (partial)
  • debugger (partial)
  • interpreter discovery (partial)
  • import sorting (partial)
  • code execution / terminal
  • (datascience?)
• currently do spawn():
  • [ ] old debug adapter (launch)
• ensure that (at this point) the extension only uses PythonExecutionFactory for running python
• [ ] old debug adapter (multi-proc case) Use conda run in the debug adapter #6010
• verify if fixes issue with Jupyter (Jupyter doesn't work with anaconda #5539)

[DonJayamanne]

Isn't this a duplicate of #6010?

[luabud]

@DonJayamanne we separated the issues for running tools and for the debugger

[DonJayamanne]

Added another item for running Jupyter (DataScience)

[DonJayamanne]

@luabud @brettcannon
I'd prefer to somehow implement this as an experiment.
I.e. roll this out slowly to users, rather than everyone in one go. This way we'll know whether it works or not. If it doesn't work or we have issues, then the number of users impacted is small.

[brettcannon]

@DonJayamanne how is this not going to be an improvement from what we are doing now? conda run is the official way to do this sort of thing now, so I'm not seeing where the worry is about it being "wrong".

[DonJayamanne]

I'm not seeing where the worry is about it being "wrong".

Just a fear of something going wrong. Nothing else. 😁