pegging node 16 in tests to v16.10.0

[jsnoble]

there are some issues with using jest with any version of node >= 6.11.0. There is a memory leak that causes the tests to expand a lot. The addition of their work around workerIdleMemoryLimit didn't seem to alleviate our problem. There are other approaches we could take but after talking to Austin we decided to just use this version of node for now.

• [Bug]: Memory consumption issues on Node JS 16.11.0+ jestjs/jest#11956

[godber]

Related to @jsnoble attempt to complete:

#3303

Here's a few other related Refs:

• [Bug]: Memory consumption issues on Node JS 16.11.0+ jestjs/jest#11956
  • https://github.com/luiz290788/jest-node-16
• vm Script memory leak in Node.js 14 / 16 nodejs/node#40014
• vm: memory leak on vm.compileFunction with importModuleDynamically nodejs/node#44211
• https://bugs.chromium.org/p/v8/issues/detail?id=12198

Classic finger pointing situation.

[jsnoble]

migrating to github action tests and scripts changes have led to better test performance. While it is still an issue it does not affect us as much right now with how tests are run