chore: update nvm to v0.40.0

[avivkeller]

This PR updates the nvm install script to v0.40.0.

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run format to ensure the code follows the style guide.
• I have run npm run test to check if all tests are passing.
• I have run npx turbo build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	❌ Failed (Inspect)		Aug 8, 2024 3:27pm

[github-actions]

Unit Test Coverage Report

Lines	Statements	Branches	Functions
	90.67% (593/654)	76.08% (175/230)	94.57% (122/129)

Unit Test Report

Tests	Skipped	Failures	Errors	Time
131	0 💤	0 ❌	0 🔥	5.29s ⏱️

[mikeesto]

Hmm, not sure why the preview deploy is failing here - seems unrelated to the diff

[AugustinMauroy]

we should do something like we had done on nodejs.dev
https://github.com/nodejs/nodejs.dev/blob/main/util-node/getNvmData.js

[ovflowd]

Random Vercel failure, redeploying.

[ovflowd]

we should do something like we had done on nodejs.dev nodejs/nodejs.dev@main/util-node/getNvmData.js

What are you talking about? We use NVM only for Husky to install Node on the environment.

[AugustinMauroy]

What are you talking about? We use NVM only for Husky to install Node on the environment.

No no no, if you go on shared code you I'll see how on nodejs.dev we did to get the dynamic version of NVM

[ovflowd]

What are you talking about? We use NVM only for Husky to install Node on the environment.

No no no, if you go on shared code you I'll see how on nodejs.dev we did to get the dynamic version of NVM

Again, this is completely unrelated to this PR and that was used to render NVM version in a specific component. This has no use over here. Please avoid off-topic.