docs: Update release process

[nzakas]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

This updates the release process to generate data for the docs site instead of pushing to the current website repo. Specific changes include:

• We no longer are copying files over into a separate repo
• gensite now generates and updates data needed by the docs site
• rule_versions.json is now generated during the release
• doc.html now uses rule_versions.json to include version information on rules pages (replaces chore: add version to rules #16022)
• generates the formatters page (replaces chore: add formatters page #16018)
• added formatters into the left hand nav
• made eslintbot the default author for the release blog post (we require an author now)
• removed dateformat as a dev dependency (no longer needed after Makefile.js simplification)

Is there anything you'd like reviewers to focus on?

Please double-check the blog post generation.

[netlify]

✅ Deploy Preview for docs-eslint canceled.

Name	Link
🔨 Latest commit	09a679b
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/62b4a45dd1c4990008dfe432

[nzakas]

This should now publish the blog post with the rest of the release.

Note: We will probably need to modify this process in some way when we do a major release. I'm not sure if we want the prerelease docs to show up at /docs/latest or somewhere else. It probably makes sense to think through that as part of the next major release. I opened an issue to track that: #16041

[mdjermanovic]

LGTM assuming that we'll update the release script on Jenkins to clone https://github.com/eslint/new.eslint.org repo instead of https://github.com/eslint/website, and that the directory name where the repo will be cloned will be eslint.org (not new.eslint.org).

[nzakas]

Yup! That’s the plan.

[btmills]

So much simpler! One (important) whitespace change, then LGTM.