Print a warning when more than 10 globals are added to the root config

[connorshea]

We should print a warning that explains that the user may want to update the globals package to match whatever version oxlint's is based off of at the moment and re-run the migration to get a simpler config. Because otherwise, you can get an extremely large oxlint config when migrating in some cases, e.g. with sveltejs/svelte#17647

[benmccann]

javascript-globals version 1.4.0:

https://github.com/oxc-project/oxc/blob/dd44b1af91aaae7521fd5b49e3d3faccdcb2b59f/Cargo.toml#L164

Uses globals 17:

https://github.com/oxc-project/javascript-globals/blob/527f16b65ff87db735bdaea8da529587b0d3000e/package.json#L3

I upgraded to 17 and it avoided creating any globals: sveltejs/eslint-config@9a6909c

It'd be ideal to ensure that the number of globals matches or the version of globals matches. There could potentially be cases where adding 1-9 globals is the wrong thing to do