Handle case when command exists but doesn't meet preconditions

[jruales]

Another partial fix for: microsoft/vscode#252415

[Copilot]

Pull Request Overview

This PR improves handling of VS Code commands that exist but have unmet preconditions. The changes provide better error messaging and fallback behavior when commands cannot be executed due to precondition failures.

Key changes:

• Enhanced error handling in VSCodeCmdTool to differentiate between non-existent commands and commands with unmet preconditions
• Updated vscodeContext.ts to always fetch commands without precondition filtering, ensuring more commands are discoverable
• Improved error messages with consistent formatting (added backticks around command names)

Reviewed Changes

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

File	Description
src/extension/tools/node/vscodeCmdTool.tsx	Fixed typo (allcommands → allCommands), added fallback logic to check if command exists when preconditions aren't met, and improved error message consistency with backticks
src/extension/context/node/resolvers/vscodeContext.ts	Changed to fetch commands without precondition filtering and added fallback to open command palette when command is not found

Comments suppressed due to low confidence (1)

src/extension/context/node/resolvers/vscodeContext.ts:78

• Corrected grammar from '1 arguments' to '1 argument'.

				// We only know how to handle 1 arguments