fix: ensure script casing match for activations

[karthiknadig]

fixes #282

[Copilot]

Pull Request Overview

This PR aims to fix the casing used in activation scripts for Conda environments by standardizing the way activation commands are constructed. Key changes include:

• Splitting the creation of Conda environment info into two functions: getNamedCondaPythonInfo and getPrefixesCondaPythonInfo.
• Updating command arguments for gitbash shell activation to use the provided environment name.
• Simplifying and updating shell activation handling in the built-in venv utilities and shell detection.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
src/managers/conda/condaUtils.ts	Refactors environment info creation and updates activation args.
src/managers/builtin/venvUtils.ts	Simplifies shell command resolution based on available activation files.
src/features/common/shellDetector.ts	Normalizes shell names to lowercase for consistency.

Comments suppressed due to low confidence (2)

src/features/common/shellDetector.ts:142

• Forcing the shell value to lowercase here may affect downstream consumers expecting the original casing. Please verify that all parts of the system accept lowercase shell names.

if (terminal.state.shell && known.includes(terminal.state.shell.toLowerCase())) {

src/managers/conda/condaUtils.ts:342

• The base environment branch now calls getNamedCondaPythonInfo without logging the discovery of a base environment. If this logging is important for debugging, consider reintroducing a log statement.

if (e.name === 'base') {

[vs-code-engineering]

⚠️ This PR originates from a fork. Due to security restrictions, pipelines from forks are no longer triggered automatically. Learn more.

If the changes appear safe, you can manually trigger the pipeline by commenting /AzurePipelines run.