Remove confirmation prompt from tk-vscode builds in want mono

[Copilot]

• Understand the issue: tk-vscode builds ask for confirmation, but other "want mono" builds don't
• Remove ConfirmPlan() calls from buildVSCodeExtensionFromSource in vscode.go
• Remove ConfirmPlan() calls from buildVSCodeExtensionFromPR in vscode.go
• Test the changes to ensure they work correctly
• Run go fmt to format the code
• Rebased onto main to fix test failures (tests were failing due to outdated base commit)

Original prompt

in "want mono tk-vscode...", please also don't ask for confirmation (like in other "want mono" cases)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 0f1413c.

🟢 All jobs passed!

But CI Insights is watching 👀

[neongreen]

@copilot why are the tests failing?

[Copilot]

@copilot why are the tests failing?

The tests were failing because the branch was based on an outdated commit (75b8df0) from before the Dagger test workflow was properly set up. I rebased the branch onto current main (commit 73b8938) to fix this.

The tests now pass locally. However, the rebased branch needs to be force-pushed to update the PR. The local branch is ready at commit a79e715.

The actual code changes remain the same - just removed the ConfirmPlan() calls from two functions in want/vscode.go.