feat!: requires node.js >=20 & eslint >= 9.39.2

[aladdin-add]

refs: #502

[MichaelDeBoey]

Until now, our Node version is always in line with latest stable ESLint version and supported ESLint versions are always in line with latest typescript-eslint version
So for now that means: keeping Node in line with ESLint v9 (^18.18.0 || ^20.9.0 || >=21.1.0) + keeping ESLint in line with typescript-eslint (^8.57.0 || ^9.0.0)

Only exception here is eslint-plugin-eslint-plugin, which always dropped a new major release just before a major ESLint release.
Here we always only supported latest ESLint version and up + Node versions aligned with upcoming ESLint version.

The current version of this plugin is in line with both latest stable ESLint & typescript-eslint versions.
This PR would be a major release, so I think it's fine to update Node support to be in line with ESLint v10 (^20.19.0 || ^22.13.0 || >=24).

I don't see any point in dropping support for any ESLint version lower than latest (v9.32.0) tbh.
Imo, we should keep it as close as possible to v9.0.0
Since we're always in line with typescript-eslint, I would wait for them to see which versions they want to keep supporting and align with them (as we always did in the past)
More context will probably given in typescript-eslint/typescript-eslint#11952
CC/ @JoshuaKGoldberg

[aladdin-add]

tbh, I also think it's a bit too radical to drop support for eslint<v9.39.2. I referred to the strategy of tseslint v8, but let's wait and see what they decide when it comes to v9. :)