fix: support callv and proxies for lsp.js

[ajbt200128]

Previously we added support for proxies in #9994. But it broke LSP.js networking as we were forced to use callv to support proxies as a workaround, and callv isn't supported in cohttp-jsoo!. So we have to patch callv and patch our XHR js library to enable proxies for this stuff. I'm going to try and make a bunch of PRs to cohttp and ca-certs etc to fix this upstream, but for now we have this fix.

Test plan

For testing js w/out proxy

make build-semgrep-jsoo-debug
make -C js build
make -C js test

For testing JS + proxy

make build-semgrep-jsoo-debug
make -C js build
make -C js/language_server
# copy js/language_server/dist into extension
# Run vscode with proxy and Use JS to confirm it works

TODO add MIT license to VSCode

[github-actions]

PR checklist:

• Purpose of the code is evident to future readers
• Tests included or PR comment includes a reproducible test plan
• Documentation is up-to-date
• A changelog entry was added to changelog.d for any user-facing change
• Change has no security implications (otherwise, ping security team)

If you're unsure about any of this, please see:

• Contribution guidelines!
• One of the more specific guides located here

[github-actions]

📸 The pytest shapshots changed in your PR.
Please carefully review these changes and make sure they are intended:

1. Review the changes at 5910465

2. Accept the new snapshots with

   git fetch origin && git cherry-pick 5910465 && git push
   

[github-actions]

📸 The pytest shapshots changed in your PR.
Please carefully review these changes and make sure they are intended:

1. Review the changes at 0a1d9a9

2. Accept the new snapshots with

   git fetch origin && git cherry-pick 0a1d9a9 && git push
   

[github-actions]

📸 The pytest shapshots changed in your PR.
Please carefully review these changes and make sure they are intended:

1. Review the changes at 6bf3b9c

2. Accept the new snapshots with

   git fetch origin && git cherry-pick 6bf3b9c && git push
   

[github-actions]

📸 The pytest shapshots changed in your PR.
Please carefully review these changes and make sure they are intended:

1. Review the changes at 6716786

2. Accept the new snapshots with

   git fetch origin && git cherry-pick 6716786 && git push
   

[kopecs]

Suggested change

ignore uri;

Dead now?

[kopecs]

Seems mostly good. I think we would benefit from some more documentation.

[github-actions]

📸 The pytest shapshots changed in your PR.
Please carefully review these changes and make sure they are intended:

1. Review the changes at 1bf0502

2. Accept the new snapshots with

   git fetch origin && git cherry-pick 1bf0502 && git push
   

[github-actions]

📸 The pytest shapshots changed in your PR.
Please carefully review these changes and make sure they are intended:

1. Review the changes at 3effa81

2. Accept the new snapshots with

   git fetch origin && git cherry-pick 3effa81 && git push
   

[github-actions]

📸 The pytest shapshots changed in your PR.
Please carefully review these changes and make sure they are intended:

1. Review the changes at 016a54d

2. Accept the new snapshots with

   git fetch origin && git cherry-pick 016a54d && git push
   

[r2c-argo]

semgrep-compare-github-uwue0 results

Ran benchmark on 38 repositories

The number of findings differs for 3 repos

Whole benchmark is 6.5% faster (a bit of noise is expected)

Relative speed improvement is 1.01 on average

• 3% of scans are significantly faster

Relative memory improvement is 1.00 on average

• 3% of scans use significantly less memory

[github-actions]

📸 The pytest shapshots changed in your PR.
Please carefully review these changes and make sure they are intended:

1. Review the changes at 64be254

2. Accept the new snapshots with

   git fetch origin && git cherry-pick 64be254 && git push
   

[ajbt200128]

pro checks failing seem unrelated