Windows Certificates: bundle roots.exe

[olafurpg]

Fixes CODY-2176

Previously, we used the win-ca "fallback" method to install local certificates. We used the fallback because we use esbuild to bundle the Cody VSC extension, which breaks automatic detection of a roots.exe binary that is included with the win-ca npm package. In the latest VS Code Insiders, this no longer works and causes Cody to fail all network requests. This PR is an attempt to fix this problem by removing the "fallback", bundling the roots.exe binary along with the Cody extension and adding logic to compute the file path of the bundled roots.exe at runtime (via vscode.ExtensionContext).

Test plan

• Get a Windows computer
• Install latest VS Code Insiders
• Install the latest Cody pre-release and reproduce the actual bug (network requests fail)
• Checkout this branch and run from the vscode/ sub-directory

  .\node_modules\.bin\vsce package --no-dependencies --pre-release --no-update-package-json --no-git-tag-version --out .\dist\cody.vsix

• Run "Install from VSIX" command from VS Code insiders and pick dist\cody.vsix
• Reload and confirm that network requests work as expected
• I don't know how to verify this, but it would be good to test it actually respects local certificates. I only confirmed that win-ca doesn't crash.

[olafurpg]

This PR fixed the network errors I was able to reproduce on a vanilla installation on Windows with VS Code Insiders. If self-signed local certificates are not working then we should open a separate feature request for that. Most importantly, we can't break the experience for all Windows users to support this functionality (which isn't working in the first place)