Upgrade to Node 16

[cheehongw]

Given that node 14 (and 16 for that matter) have been deprecated, perhaps it might be a good time to start upgrading to a version >16 and resolve dependency issues for packages. WDYT? @CATcher-org/developers

Originally posted by @vigneshsankariyer1234567890 in #1191 (comment)

As mentioned by Vignesh, we should start upgrading to Node16+.

Let's upgrade to the next LTS version (Node 16) and resolve any dependency issues along the way.

With the upgrade from Node 14 to Node 16, we are also moving from npm6 to npm8

Potentially useful links:

• Use LTS version Node v14 instead of Node v12 as default #964
• https://github.blog/2021-02-02-npm-7-is-now-generally-available/
• https://nodesource.com/blog/whats-new-in-npm-8/

To-do:

• Bump failing libraries
• Update workflows to use Node 16
• Update dev documents to recommend Node 16

[cheehongw]

it appears that Angular 10 (more specifically angular/cli) does not support Node 16 just yet :)

We will need to upgrade to at least Angular 13 before moving over to Node 16.

See the commit message here:
angular/angular-cli@9fe5575