chore: upgrade dependencies

[Josh-Cena]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

See related discussion in #7455. Should we even go straight to Node 16?

Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/

Related issues/PRs

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	2ef8975
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/6290c5d98af4570008c7484c
😎 Deploy Preview	https://deploy-preview-7463--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟢 93	🟢 100	🟢 100	🟢 100	🟢 90	Report
/docs/installation	🟢 91	🟢 99	🟢 100	🟢 100	🟢 90	Report

[github-actions]

Size Change: +48 B (0%)

Total Size: 796 kB

Filename	Size	Change
website/build/assets/js/main.********.js	599 kB	+48 B (0%)

ℹ️ View Unchanged

Filename	Size
website/.docusaurus/globalData.json	52.3 kB
website/build/assets/css/styles.********.css	106 kB
website/build/index.html	38.9 kB

_{compressed-size-action}

[slorber]

Should we even go straight to Node 16?

As discussed in the other RFC issue (#7455): 👍

I'd rather do this in another PR with only the Node.js bump:

• Require Node 16.0
• Add explicit 16.0 in GitHub Action test matrix (we currently don't test for the exact minimum version, but probably should).

['16.0', '16', '18'] matrix should be fine. If 16.0 does not work let's use another minor then?

[Josh-Cena]

Yes, 14.15 is required for this merge, but we can do 16 in another PR, that's the plan, right?

[slorber]

My thought was to merge v16 now and then this PR (smaller, not bumping any Node.js version), but if you want to do the other way, no problem 😄

[Josh-Cena]

Ah, let's do it the other way round, then. No problem!

[Josh-Cena]

Going to upgrade other minor dependencies in the batch as well, since this no longer depends on a Node version bump

[Josh-Cena]

Blocked on #7422 so we can upgrade babel-plugin-dynamic-import-node (although the plan is to eventually remove it)