MDL-81125 core: Add tooling to generate developer upgrade notes

Usage:

    node .grunt/upgradenotes.mjs

      OR

    npm run upgradenote

Arguments can be provided to specify the issue number, component,
message, and type of change.

    node .grunt/upgradenotes.mjs -- \
        -c [component] \
        -i [issue number] \
        -t [type] \
        -m [message]

        OR

    npm run upgradenote -- \
        -c [component] \
        -i [issue number] \
        -t [type] \
        -m [message]

Summary Markdown files can be created using:

    node .grunt/upgradenotes.mjs summary

Weekly release files can be created using:

    node .grunt/upgradenotes.mjs release

Final release files can be created using:
using:
    node .grunt/upgradenotes.mjs release [version]

Generally speaking the integration team will be responsible for updating
the UPGRADING.md notes as part of the weekly integration processes.

package.json

@@ -2,6 +2,9 @@
   "name": "Moodle",
   "private": true,
   "description": "Moodle",
+  "scripts": {
+    "upgradenote": "node .grunt/upgradenotes.mjs create"
+  },
   "devDependencies": {
     "@babel/core": "7.17.5",
     "@babel/eslint-parser": "^7.21.3",
@@ -13,6 +16,8 @@
     "babel-plugin-system-import-transformer": "^4.0.0",
     "babel-plugin-transform-es2015-modules-amd-lazy": "2.0.1",
     "babel-preset-minify": "0.5.1",
+    "chalk": "^5.3.0",
+    "commander": "^12.0.0",
     "cross-env": "^7.0.3",
     "docdash": "^2.0.2",
     "eslint": "^8.56.0",
@@ -30,6 +35,8 @@
     "grunt-stylelint": "^0.19.0",
     "hugo-bin": "^0.80.2",
     "hugo-lunr-indexer": "^1.1.3",
+    "inquirer": "^9.2.15",
+    "inquirer-search-list": "^1.2.6",
     "jsdoc": "^4.0.2",
     "jsdoc-to-markdown": "^8.0.0",
     "jshint": "^2.13.4",
@@ -42,6 +49,7 @@
     "shifter": "https://github.com/andrewnicols/shifter/archive/v1.2.0_moodle-0.tar.gz",
     "stylelint": "^15.11.0",
     "stylelint-csstree-validator": "^3.0.0",
+    "winston": "^3.13.0",
     "xpath": "0.0.32"
   },
   "engines": {