Improve micromamba support

[0x0L]

Setting python.condaPath to /usr/local/bin/micromamba mostly works.

However it fails activating the env properly when creating a new terminal:
because of the reported version (1.3.1 < 4.4), the extension uses "activate" instead of "{python.condaPath} activate"

It would be great if that could be fixed

[karthiknadig]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[karrtikr]

Fix should be out in the pre-release version of the extension in a day, use the following to try it out:

[philippemiron]

@karrtikr I'm not sure this PR solves the issue. It seems like it assumes that conda is available with micromamba.

[karrtikr]

We do not support micromamba officially. This just is a patch fix user asked in the original request to make it work correctly for that scenario.

If you would like for us to support micromamba please open a new feature request.

[philippemiron]

The original request was to make activate works with micromamba, which requires calling micromamba activate env, not calling conda.

[karrtikr]

because of the reported version (1.3.1 < 4.4), the extension uses "activate" instead of "{python.condaPath} activate"

The original request #20756 (comment) asks us to use "{python.condaPath} activate", so that when python.condaPath is set to /usr/local/bin/micromamba, activation works for micromamba.