Update dependencies

[TheJaredWilcurt]

• Updated all dependencies
  • Documented the one dependency I couldn't easily update
• Removed all pnpm stuff, to simplify the repo.
  • package-lock.json is from npm
  • docs now give npm instructions
  • npm scripts no longer use pnpm
  • ci/cd uses npm ci
• Updated GHA to use the package-lock.json

[TheJaredWilcurt]

npm ci will install the exact modules listed in the package-lock.json file. So you know that your published version will work exactly the same as it did for you locally. Without a lock file, or using npm install (which updates the lock file), you can end up with a sub-dependency at a different version which may cause unforeseen issues.

npm ci basically solves the "works on my machine" issue. Now it works on all machines.

[TheJaredWilcurt]

Unfortunately JSON files do not support comments. So I've added this section here, so documentation around the package.json file can still occur.

If you think package.json files should be more permissive to allow for comments, you can +1 this post:

• [RRFC] Opt-in solution to support comments in package.json (among other features) npm/rfcs#291

[TheJaredWilcurt]

File Changes:

• node => node-version, most repos name the node matrix this, don't know why, but just making it like the rest.
• npm 8.5.0 - By default Node 14 comes with npm 6, which supports v1 lock files. But this PR includes a V2 lockfile. So we need to use npm 7 or above for that.
• actions-setup-node => volta-cli/action, This lets us easily set the Node and npm versions in one go, so we can do Node 14, 16, or 18 all with npm 8.5.0
• npm run install => npm ci, this makes sure we download the exact same dependency versions that were used during development

[ayushmanchhabra]

LGTM!