🚀 Feature: Bring in eslint-plugin-node-dependencies's compat-engines rule

[JoshuaKGoldberg]

Splitting out from #43 (comment) & #42: eslint-plugin-node-dependencies has a compat-engines rule. Let's merge it into this package!

https://ota-meshi.github.io/eslint-plugin-node-dependencies/rules/compat-engines.html

Blocked on #40, but once that PR is merged this will be good to go. ✅

[michaelfaith]

I'm curious what this rule would add to the picture when package manager's will already provide feedback (or error if strict is enabled) when the engines conditions aren't met?

[JoshuaKGoldberg]

I like having this and other rules act as a "first round" of warnings before you have to run the package manager. This way you get feedback in the editor before having to go through a full installation attempt.

[lishaduck]

I'm curious what this rule would add to the picture when package manager's will already provide feedback (or error if strict is enabled) when the engines conditions aren't met?

The biggest issue is that the package manager will only enforce the current node version.
So if you develop on Node 24, but support back to, say, Node 16, you won't get warnings (unless you use nodeVersion with pnpm, but that's an obscure feature most people don't know to use).