Bring in dependency banning and/or restricting rule(s)

[JoshuaKGoldberg]

Splitting out from #42: npm-package-json-lint has a family of rules that can ban variants of package dependencies:

• https://npmpackagejsonlint.org/docs/rules/dependencies/no-restricted-dependencies
• https://npmpackagejsonlint.org/docs/rules/dependencies/no-restricted-devDependencies
• https://npmpackagejsonlint.org/docs/rules/dependencies/no-restricted-pre-release-dependencies
• https://npmpackagejsonlint.org/docs/rules/dependencies/no-restricted-pre-release-devDependencies

Additionally, other rules exist in that package and elsewhere for restricting dependency ranges:

• https://github.com/kellyselden/eslint-plugin-json-files/blob/master/docs/rules/no-branch-in-dependencies.md
• https://github.com/kellyselden/eslint-plugin-json-files/blob/master/docs/rules/restrict-ranges.md

I'd like to add in some kind of rule or rules to this package equivalent to those. Not clear yet how they'd look. Should they be one big configurable rule? Granular rules like how npm-package-json-lint & co have them? More thought required.

Blocked on #40. Not a high priority issue given that this wouldn't be enabled by default in any recommended configs. ✅

[MorrisonCole]

I'd love to see this - definitely something missing from the eslint ecosystem at the moment!

https://eslint.org/docs/latest/rules/no-restricted-imports#rule-details might be a good reference too, since it does something similar.

Some granularity would be nice - one thing I've struggled with in large monorepos is gradually phasing out a dependency, which requires having warnings for some dependencies (i.e., those being removed), and errors for others (i.e., those already removed) in parallel.