Upgrade to use node 16

[yucheng11122017]

What is the purpose of this pull request?

• Documentation update
• Bug fix
• Feature addition or enhancement
• Code maintenance
• DevOps
• Improve developer experience
• Others, please explain:

Resolves #2197

Overview of changes:
Update CI scripts and documentation mention of the node.js version to 16

• all user-facing functionalities are working
• no issues with the development setup
• whether related GitHub Actions need to be updated
  • PR opened for Github Actions opened updating version numbers
  • Deploying to github pages and surge upon push, build upon push, deploy review upon PR, reusable workflow is fine
• any deprecated syntax to be refactored
  • None of the deprecated syntax is being used by markbind
• docs are updated
• Deployment to Netlify/other platforms is ok
  • PRs opened for netlify repos [PR1, PR2]to update version number
  • Currently unable to check deployment to Travis due to an error with account. This is currently unresolved by Travis
  • Deploying with Netlify, AppVeyor, Circle, Github Pages is ok

Anything you'd like to highlight/discuss:

Testing instructions:

Proposed commit message: (wrap lines at 72 characters)
Upgrade nodejs to v16

---

Checklist: ☑️

• Updated the documentation for feature additions and enhancements
• Added tests for bug fixes or features
• Linked all related issues
• No unrelated changes

Breaking change descriptions:
Node.js version 14 is no longer supported by Markbind as it is due to reach it's end of life in 30 April 2023. The minimum required version of Node.js is now 16.
Users are to upgrade to at least version 16 of Node.js.

[ong6]

There are a few instances in docs/userGuide/deployingTheSite.md where the node version is set to 10. Perhaps we can update those too for consistancy. For example in the **Configuring your repository in Travis CI** section as well as the other sections below

[yucheng11122017]

There are a few instances in docs/userGuide/deployingTheSite.md where the node version is set to 10. Perhaps we can update those too for consistancy. For example in the **Configuring your repository in Travis CI** section as well as the other sections below

Updated in cc7d97a! :)

[tlylt]

Almost there, thanks @yucheng11122017, will aim to merge this one in soon. Btw can we include a page in our DG, perhaps something similar to "Migrating to TypeScript", to list out a checklist of things to do/check when migrating? I think your description is already quite comprehensive, can copy over and start from there.

[yucheng11122017]

Almost there, thanks @yucheng11122017, will aim to merge this one in soon. Btw can we include a page in our DG, perhaps something similar to "Migrating to TypeScript", to list out a checklist of things to do/check when migrating? I think your description is already quite comprehensive, can copy over and start from there.

Ok! I will open a new issue for this

Edited: Opened #2246

stale