:UP: upgrade to latest Node LTS

[nilsnh]

Fixes #55 .

Milestone

Stop being locked to Node v14, and just start tracking the latest Node LTS release.

Getting there

1. Use NVM configuration syntax to select latest Node LTS release.
2. Removing NPM config so that it will track the LTS Node version.
3. Removing Netlify function version specification so that it will just use latest LTS release.
4. Also, I saw some warnings in the Netlify build log related to esbuild for function bundling which is beta functionality. I tried to fix it but eventually gave up and removed it from the build step. Esbuild didn't really provide us with any needed functionality there. See: https://github.com/EthicalSource/hippocratic-license-3/pull/57/commits/31cb93cafe1c291ad0f08c9e7084105f0927fb43

Interesting bits

• Moving forward we should just have the latest LTS release for this code. So we shouldn't have to keep coming back to update this.
• Worth noting that all NPM dependencies are pinned to specific version numbers, and we have been quite conservative about how many dependencies we have included.
• Node only runs in the build step and in the Netlify lambda functions.

What I need help with

• Just another pair of eyes to check that overall functionality hasn't broken.

What's next

After merging, this PR should allow us to:

• Do less security maintenance work.

[netlify[bot]]

✅ Deploy Preview for firstdonoharm ready!

Name	Link
🔨 Latest commit	31cb93cafe1c291ad0f08c9e7084105f0927fb43
🔍 Latest deploy log	https://app.netlify.com/sites/firstdonoharm/deploys/62d586634d01b400089965ea
😎 Deploy Preview	https://deploy-preview-57--firstdonoharm.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.