Gate IDE extension checks behind active developer profile

[codeforester]

Problem

Ubuntu acceptance for basectl ci check base-demo is blocked by manifest-declared VS Code extension checks when the Ubuntu VM does not have the code CLI on PATH. The core Ubuntu setup path is otherwise healthy: apt prerequisites, uv, mise, Python runtime, and platform-aware artifacts all pass.

IDE bootstrapping is workstation/editor polish. It should remain available when the developer profile is requested, but it should not make the default Linux runtime acceptance path fail.

Proposal

• Keep manifest IDE declarations intact.
• Skip IDE extension diagnostics unless the developer prerequisite profile is active.
• Continue running IDE extension checks when --profile dev is selected.
• Document the profile boundary in the IDE/Linux support docs.

Acceptance Criteria

• basectl check/ci check <project> without --profile dev does not fail solely because IDE extension CLIs such as code are missing.
• basectl check/doctor <project> --profile dev still reports missing IDE extension CLI/extension diagnostics.
• Existing IDE setup behavior remains available for explicit developer workstation setup.

Context

Observed on Ubuntu 24.04 ARM64 under Parallels while validating base-demo: BASE_DEMO_ENV, uv, mise, Python 3.13, and tool:bats-core all passed; only missing VS Code CLI extension probes kept the check in a missing-requirements state.