🚀 Feature: Bring in a compat-peerDependencies rules

[lishaduck]

Feature Request Checklist

• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Overview

Sometimes when developing a library, you'll accidentally bump your peerDependencies range by bumping a dependency that also has a peerDependency on such and such a package.
It'd be nice to detect that and remind you to either bump your peerDependencies range or revert the upgrade.

Additional Info

Taken out of #835 (comment).
Probably trivial after #48 is implemented (same logic, just checking peerDependencies in general instead of the special case of node).

[michaelfaith]

Thanks! What kind of fix should this rule provide, if any?

[michaelfaith]

@all-contributors please add @lishaduck for ideas

[allcontributors]

@michaelfaith

I've put up a pull request to add @lishaduck! 🎉

[lishaduck]

I think a suggestion to bump the range would be helpful, but a fix would be potentially a breaking change and not to be taken lightly.

[michaelfaith]

Makes sense.