Avoid 'Pulumi IaC' extensions pack requiring YAML and Copilot, instead offer standalone and packs

[jecarlsen]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

The problem is:

1. I want Pulumi IaC debugging & tasks.
2. I do not want Preview extensions (extra overhead) nor unsigned extensions (issue Installing pulumi extensions in vs code throws signature verification failed #35)
3. I do not want extension packs unless I specifically desire all of the extensions in a pack.

Please avoid mixing the Pulumi IaC features

• https://marketplace.visualstudio.com/items?itemName=pulumi.pulumi-vscode-tools&ssr=false#overview

with Pulumi Copilot and Pulumi YAML.
I do not desire these, it brings extra overhead as in IDE extension footprint and management.

Suggestion - could we please have:

1. Pulumi Tools as an Extension-Pack
2. Pulumi IaC as standalone extension (missing today)
3. Pulumi Copilot as standalone extension
4. Pulumi YAML as standalone extension

I apologise if the tone appears a bit on the hars side, I only intend to make it clear how strong the desire is to have these separated. I'm not trying to lash out. Apologies in advance :)

Affected area/feature

VScode Extension offering of: Pulumi IaC

[EronWright]

This is a reasonable request because extensions tend to be fit-to-purpose, composable, have different lifecycles, and have different supported/target environments. For example, the ESC functionality could reasonably run in the web version of vscode. I also agree with providing an extension pack for convenience.