feat: add PromptExtensionInstallFailureAction to handle extension ins…

[vishalranaut]

fix: remove duplicate disable options in extension button dropdown

Fixes #244138

---

Problem

When a VS Code extension is disabled both globally and for the workspace, the "Disable" button dropdown incorrectly shows both options at the same time:

• "Disable"
• "Disable (Workspace)"

This is confusing because one or both states are already applied — showing them again implies the user can disable something that is already disabled.

Root cause

The dropdown action list was being built without checking the extension's current disabled state. Both actions were always added regardless of whether the extension was already globally disabled, workspace-disabled, or enabled.

Fix

Added conditional checks before pushing each action into the dropdown list:

• If already disabled globally → do not show "Disable"
• If already disabled for workspace → do not show "Disable (Workspace)"
• If enabled → show both options as normal (existing behaviour)

File changed: src/vs/workbench/contrib/extensions/browser/extensionsActions.ts

---

Before

Dropdown always showed both "Disable" and "Disable (Workspace)" regardless of state.

After

Dropdown only shows the disable options that are actually applicable to the current extension state.

---

Checklist

• I have read the Contributing Guide
• Code follows the existing TypeScript patterns in the file
• No unrelated code was reformatted
• No string labels or translations were changed
• Tested manually by disabling an extension globally, per-workspace, and in both states to verify correct dropdown options appear

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Filters hidden actions from the Manage Extension dropdown menu and removes any resulting empty groups.

Changes:

• Apply hidden-action filtering to each group in getActionGroups
• Drop groups that become empty after filtering