Extension support for environment managers

# Overview

The intent of the Python Environments extension is to enable developers to provide support for their favorite Python environment and package managers by shipping support via its own extension. This extension provides mechanisms for users to interact with environment managers to create, select, and install packages, etc. Your extension will depend on this extension for user interactions, and you can handle the various core features of the environment manager in your extension. This ensures a consistent experience for the user with specific support for each environment manager.

We are looking for community support to build and maintain these extensions!

## APIs

This extension provides a set of APIs for developers to register their own Environment and Package managers. We are also looking for feedback on the APIs. See here for more details: https://github.com/microsoft/vscode-python-environments?tab=readme-ov-file#api-reference-proposed

## Help wanted

### Environment manager

| Env manager | Status |
| --- | --- |
| `venv` | Built-in [1] |
| `conda` | Expecting community extension [2] |
| `poetry` | Expecting community extension |
| `pyenv` | Expecting community extension |
| `pixi` | [In progress](https://github.com/jjjermiah/pixi-vscode) @jjjermiah |
| `hatch` | [In progress](https://github.com/flying-sheep/vscode-hatch) @flying-sheep |
| `pipenv` | Expecting community extension |
| `uv` | Expecting community extension |
| `activaState` | Expecting community extension |

[1]: `venv` (built-in) will use `uv` if available for environment creation, package install and delete.
[2] : We have demo support for `conda` to show case some of the features of the extension. But we are expecting community extension for full featured support (like for example stacked envs in conda)

### Package manager

| Package Manager | Status |
| --- | --- |
| `pip` | Built-in |
| `conda` | Expecting community extension [1] |

[1] : We have demo support for `conda` to show case some of the features of the extension. But we are expecting community extension for full featured support.

Comece pela referência de API proposta e vinculada na issue e compare as tabelas de environment-manager e package-manager. Escolha um manager e determine o suporte completo esperado por meio das APIs de registro; a conclusão exigiria uma extensão da comunidade mantida, mas a issue não menciona arquivos do repositório nem testes.

Escrita pelo modelo de indexação a partir do texto da issue.