Bump node to version 16

[WiNloSt]

Why?

1. Fixes frontend test failures related to nock library
2. Enforces the same version for dev and production environments

---

Since the introduction of nock in #27337, we starts to see some inconsistency in the unit tests behavior run on Node v14 vs v16+. This leads to the conclusion that we should be using Node v16+ for both development + CI environment to make the tests more repeatable.

Also, please note that we're using exactly Node 16.10.0 on our CI since a lot of people reported here jestjs/jest#11956. Any other 16 or 18 versions don't seem to work at all.

Example failed runs

• https://github.com/metabase/metabase/actions/runs/4047552648/jobs/6961708453

Other runs are hard to find since the PR is amended, but there was at least a single commit that I reran the tests a few times and it failed consistently when this couldn't be reproduced on machines using node V16+

[WiNloSt]

This was introduced in #27337, but doesn't seem to be needed to work in Node v16+ anymore

[codecov]

Codecov Report

Base: 66.26% // Head: 66.26% // No change to project coverage 👍

Coverage data is based on head (5ae802f) compared to base (9ef4161).
Patch has no changes to coverable lines.

❗ Current head 5ae802f differs from pull request most recent head 707a478. Consider uploading reports for the commit 707a478 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #27970   +/-   ##
=======================================
  Coverage   66.26%   66.26%           
=======================================
  Files        3283     3283           
  Lines       95174    95174           
  Branches    12141    12141           
=======================================
  Hits        63069    63069           
  Misses      27083    27083           
  Partials     5022     5022           

Flag	Coverage Δ
back-end	85.29% <ø> (ø)
front-end	48.69% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[deploysentinel]

No failed tests 🎉

[WiNloSt]

There are still problem presents when upgrading node version to 16 or 18.

1. Only upgrading the Node version will fail the unit tests due to memory error

   FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

2. Then I tried running it with NODE_OPTIONS="--max-old-space-size=4096" which suppress the error, now the tests don't raise any error, but are frozen instead.

So, there are still some stuff left to investigate about a proper and better fix. Now we'll just delete the unit failed unit tests as a short term solution.

[kulyk]

Oops, I accidentally clicked "delete branch" 🤦‍♂️

[WiNloSt]

@kulyk I was going to do it anyway. No worries!

[WiNloSt]

Lots of people reported that they need to use exactly version 16.10.0 to not crash on their CI.

[nemanjaglumac]

I'd maybe add a comment in the code here so we don't forget about this and change it by mistake.
If you decide to do that, please commit with [ci skip] and I'll force-merge it.

[WiNloSt]

done!

[nemanjaglumac]

🚀