Add basic Poetry environment lifecycle support

[Eduardo Villalpando Mello (edvilme)]

Summary

• add basic Poetry environment creation for existing projects using a selected global Python 3 interpreter
• add Poetry environment removal with owning-project detection and selection/cache cleanup
• add lifecycle unit coverage for creation, package failures, reused environments, removal, and multi-project associations

Validation

• npm run lint
• npm run compile-tests
• npm run unittest

[Copilot]

Pull request overview

Adds basic Poetry environment creation and removal for existing Python projects.

Changes:

• Creates Poetry environments using global Python 3 interpreters.
• Removes environments and clears cached selections.
• Adds localized lifecycle messages and unit coverage.

Reviewed changes

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

File	Description
src/managers/poetry/poetryManager.ts	Implements Poetry lifecycle operations.
src/managers/poetry/main.ts	Supplies the output channel.
src/common/localize.ts	Adds lifecycle messages.
src/test/managers/poetry/poetryManager.createRemove.unit.test.ts	Tests creation and removal flows.

Suppressed comments (1)

src/managers/poetry/poetryManager.ts:208

• After deleting the project mapping, get(root) falls back to globalEnv, but this event always reports new: undefined. When a different global Poetry environment exists, listeners receive a selection that disagrees with the manager's actual result. Report that fallback, except when the global environment is the one being removed.

                        new: undefined,

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.