ci: Remove Node 16 CI prerelease workaround (refs #14933)

[btmills]

Prerequisites checklist

• I have read the contributing guidelines.

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

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

What changes did you make? (Give an overview)

Several dev dependencies have a peer dependency on the local ESLint. Prereleases don't satisfy regular version range constraints, so the new peer dependency resolution algorithm in Node 16 rejects v8.0.0-beta.0 as a valid peer dependency. Until we're done with prereleases, we can use the --force flag to force npm to accept that the prerelease satisfies the peer dependency.

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

Once we release v8.0.0 stable, we can merge this PR. When we do, we should also remove --force from the build script in Jenkins.

[btmills]

We no longer need --force for our circular dependency, but eslint-plugin-jsdoc doesn't include 8.0.0 in its peer dependency range yet, so we need to keep --force for now.

[btmills]

eslint-plugin-jsdoc@37.0.0 was released with eslint@^8.0.0 in its peerDependencies, so this is now unblocked!

Note to whomever merges this: we can also remove --force from the Jenkins build script.

[aladdin-add]

LGTM~

[mdjermanovic]

LGTM, thanks!

[mdjermanovic]

When we do, we should also remove --force from the build script in Jenkins.

I removed --force from the eslint Release and both data fetches scripts in Jenkins.