Update Node version to v18

[gerteck]

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:

Overview of changes:

MarkBind aims to support up to the last maintainence lts release, which is Node.js 18 up to Apr 2025.

This PR seeks to upgrade Node.js to Node 18.

• Relevant MB documentation on Node.js migration
• Previous upgrading Node 14 -> 16 PR

Addresses and Fixes #2541

Anything you'd like to highlight/discuss:

Before the version update, check that

• any deprecated syntax to be refactored
• all user-facing functionalities are working
• no issues with the development setup
• update related GitHub Actions and workflows
  • Test updated Actions
• docs are updated
• Deployment to Netlify/other platforms is ok
  • Netlify (PRs 1, 2 opened for netlify quickstart repos to update node version number)
  • GH-Pages
• Deployment via CI platforms is ok
  • GH Actions test run
  • Travis CI test deployment
  • AppVeyor CI test deployment
  • Circle CI test deployment
• Update netlify.toml

Related PRs:

• Update MarkBind Action node version to 18 markbind-action#17
• Update Node version to 18 init-typical-netlify#6
• Update Node Version to 18 init-minimal-netlify#6

Related Changes

• Update Vue-Jest dev Dependency for Vue Components Package #2565
  • (Resolves Document: Node LTS (v20) and python 3.12 does not work on MarkBind install #2496)
• Chore (docs): Add getting started warning for python 3.12 with node LTS #2536 (Changes Reverted)

Other:
Node.js Changelogs

• Node v17.0
• Node v18.0

Predecessor Closed PR

• Update Node version to 20 #2569

Thanks to @tlylt for making the new release, have been able to test the various CI platforms with success.

Testing instructions:

Proposed commit message: (wrap lines at 72 characters)

Upgrade Node.js to v18

---

Checklist: ☑️

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

---

Reviewer checklist:

Indicate the SEMVER impact of the PR:

• Major (when you make incompatible API changes)
• Minor (when you add functionality in a backward compatible manner)
• Patch (when you make backward compatible bug fixes)

At the end of the review, please label the PR with the appropriate label: r.Major, r.Minor, r.Patch.

Breaking change release note preparation (if applicable):

• To be included in the release note for any feature that is made obsolete/breaking

Give a brief explanation note about:

• what was the old feature that was made obsolete
• any replacement feature (if any), and
• how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

[tlylt]

Thanks @gerteck! Will take a look over the weekend

[tlylt]

LGTM