[ENHANCEMENT] Disable other extensions when launching the Extension Development Host for debugging

[daewoongoh]

Problem (one or two sentences)

When launching the Extension Development Host via the "Run Extension" debug configuration, other extensions already installed in the developer's VS Code are also loaded, which can interfere with debugging Zoo Code.

Context (who is affected and when)

Affects contributors debugging Zoo Code locally with F5 (Run Extension). It's most noticeable when the developer has other extensions installed that log output, register commands, or otherwise interact with the workspace, making it harder to isolate behavior specific to Zoo Code.

Desired behavior (conceptual, not technical)

Launching the Extension Development Host for debugging should only activate Zoo Code, without loading any other installed extensions.

Constraints / preferences (optional)

Should only affect the local debug launch configuration; no impact on the packaged extension or end-user experience.

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Proposed approach (optional)

Add the --disable-extensions argument to the "Run Extension" configuration in .vscode/launch.json.