chore: update node version to active LTS (DET-7046)

[johnkim-det]

Description

Updating node from v12.14 to v16.14.2

Also updating npm version to latest, v8.7.

Test Plan

should not require additional testing as long as everything builds and regression tests pass

Commentary (optional)

Updating from npm v8.5 to v8.7 requires one of two solutions:

• add an .npmrc file with a line that sets legacy-peer-deps=true ([BUG] non-previosly seen peer-dependency errors popping up in 8.6.0 npm/cli#4664)
  OR
• replace craco-sass-resources-loader devDependecy with a fork, @jonny1994/craco-sass-resources-loader

Checklist

• User-facing API changes need the "User-facing API Change" label.
• Release notes should be added as a separate file under docs/release-notes/.
  See Release Note for details.
• Licenses should be included for new code which was copied and/or modified from any external code.

[netlify]

✅ Deploy Preview for determined-ui ready!

Name	Link
🔨 Latest commit	18c6bb5
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/6261bc1c2459280008619f38
😎 Deploy Preview	https://deploy-preview-3932--determined-ui.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.

[hamidzr]

I added some comments but overall LGTM.

If we go with the legacy npm config option, it'd be good to see when we can take the added option out.
From a search I did previously it looked like we should be able to get rid of it once react-scripts & CRA release new versions and craco adopts them

https://github.com/gsoft-inc/craco/releases/tag/v7.0.0-alpha.0

[hamidzr]

nit: match CONTRIBUTING.md ?

[hamidzr]

It'd be ideal to see if we can upgrade our packages so we don't need this but it sounds like this is a good step forward and strictly a win.

https://github.blog/2021-02-02-npm-7-is-now-generally-available/#peer-dependencies

You have the option to retry with --force to bypass the conflict or --legacy-peer-deps command to ignore peer dependencies entirely (this behavior is similar to versions 4-6).

[hamidzr]

could you also please check that storybooks builds (dev & production) are not affected?

[johnkim-det]

i think we need legacy-peer-deps to address a peer dependency error that shows up with the storybook build anyway, so i'm going to stick with using that for now, instead of the fork. not sure if there's anything we can do on our end about the storybook issue.