Use HTTP1.1 to download nodejs package

[crazytonyli]

Issue

Sometimes on CI, we got the following error (here is an example) from installing node:

curl: (92) HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)

Even though the error is originated from nvm, but it doesn't appear to be an issue in nvm. The same issue appears in n too, which is a similar tool as nvm. And, it's likely an issue in the node.js package CDN (https://nodejs.org/dist).

Changes

I have added a new curlrc option to the nvm plugin, so that we can pass extra curl arguments to the curl commands invoked by nvm. This PR set the new option to --http1.1, which should make nvm downloads nodejs packages using HTTP1.1 instead of HTTP2 protocol, which hopefully would resolve the aforementioned errors on CI.

Test Instructions

This PR can be merged as long as CI jobs pass.

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.

[twstokes]

Makes sense! Thanks @crazytonyli. 🚀

[mokagio]

Let's see how this behaves in prod 👍 Thanks @crazytonyli

[mokagio]

For some reason, Circle CI didn't run for 63d0270. However, Circle CI run fine for other recent pushes 🤔

I think it must have been a hiccup on their end. Not sure how to restart the build, maybe a rebase and force push or a merge of trunk in here?

[crazytonyli]

@mokagio I have force-pushed but the Circle CI job still didn't run. Is it okay to ignore the CircleCI check on this PR, since only buildkite pipeline is changed?

[mokagio]

@mokagio I have force-pushed but the Circle CI job still didn't run. Is it okay to ignore the CircleCI check on this PR, since only buildkite pipeline is changed?

How odd. Yes. I'll merge this now.