chat: avoid redundant environment tool confirmation

[Eleanor Boyd (eleanorjboyd)]

Summary

• remove the extra confirmation shown before the Python environment picker
• preserve the picker's explicit user selection before creating or selecting an environment
• add regression coverage ensuring the tool does not request confirmation during preparation

Why

The contributed configurePythonEnvironment tool always returned confirmationMessages, which caused Copilot CLI sessions to stop for approval even when Allow all was enabled. The environment picker already requires the user to explicitly choose an environment action, so the preceding confirmation was redundant.

[Bill Schnurr (bschnurr)]

🔒 Automated review in progress — Bill Schnurr (@bschnurr) is auto-reviewing this PR.

[Bill Schnurr (bschnurr)]

Verification: The relevant tests could not be fully run in the isolated environment; this review is not fully verified.

Result: could-not-verify

Summary: The PR adds focused coverage for removing preparation confirmation while retaining the explicit environment picker. No tests could execute because the verification container image was unavailable. The regression test therefore remains unverified.

Test runs: 1 not run

• ⚠️ Not run | Verification preflight and test discovery | printf '%s\n' '--- changed files ---' && git --no-pager diff --name-status upstream/main...HEAD && printf '%s\n' '--- dependency state ---' && if [ -d node_modules ]; then echo 'node_modules=present'; else echo 'node_modules=missing'; fi && printf 'AUTOMATION_SANDBOX_PROFILE=%s\n' "${AUTOMATION_SANDBOX_PROFILE:-}" && printf '%s\n' '--- relevant npm scripts ---' && node -e "const p=require('./package.json'); for (const [k,v] of Object.entries(p.scripts||{})) if (/test|compile|typecheck/.test(k)) console.log(k+'='+v)" && printf '%s\n' '--- test runner grep handling ---' && sed -n '1,110p' src/test/unittests.ts && sed -n '1,95p' src/test/index.ts

⚠️ Verification preflight and test discovery diagnostic output

Container verification could not start: no trusted sandbox image is configured for microsoft/vscode-python, and local execution was not authorized.

[Bill Schnurr (bschnurr)]

Approved via Review Center.

[Bill Schnurr (bschnurr)]

Verification: The relevant tests could not be fully run in the isolated environment; this review is not fully verified.

Result: could-not-verify

Summary: The PR adds one regression test covering removal of the preparation confirmation. No tests could run because the verification container image for `microsoft/vscode-python` was unavailable and local execution was unauthorized. The change therefore could not be meaningfully verified.

Test runs: 1 not run

• ⚠️ Not run | Dependency and test discovery | git status --short && git diff --name-status "$(git merge-base HEAD upstream/main)" HEAD && node -e "const p=require('./package.json'); console.log(JSON.stringify(Object.fromEntries(Object.entries(p.scripts).filter(([k,v])=>/test|compile/.test(k)||/mocha|standardTest/.test(v))),null,2)); console.log('node_modules=' + require('fs').existsSync('node_modules')); console.log('sandbox_profile=' + (process.env.AUTOMATION_SANDBOX_PROFILE || ''));"

⚠️ Dependency and test discovery diagnostic output

Container verification could not start: no trusted sandbox image is configured for microsoft/vscode-python. Local execution was not authorized for this PR HEAD.