Remove inline eslint globals in configs

[janbrasna]

Description

These are defined in the new config since #935 and should no longer use the old format.

• I have documented this change in the design system.
• I have recorded this change in CHANGELOG.md.

Issue

#1121

Testing

CI pass on v9 should be enough to verify v10 compatibility of these removals.

[janbrasna]

The CI runs that twice:

1. /actions/runs/22524118040/job/65253378571#step:5:33
2. /actions/runs/22524118040/job/65253378571#step:6:10

and is apparently happy.

[janbrasna]

Worth noting the new globals are defined slightly differently:

protocol/eslint.config.js

Lines 124 to 132 in d20837b

	'webpack.package.build.config.js',
	'webpack.package.static.config.js',
	'webpack.test.config.js'
	],
	languageOptions: {
	ecmaVersion: 'latest',
	globals: {
	...globals.node,
	...globals.commonjs

[janbrasna]

(But then again, whatever format the webpack configs become over time, the change from es-2017 to es-latest should have no meaningful impact.) — Expecting the newer flat config values having taken precedence, they've been used like this over a year anyways FWIW.

[janbrasna]

Removed in #1133 already; closing.

[janbrasna]

Yeah not sure why GH doesn't see that as merge conflict by now, potentially by being the exact same change it's still happy to merge w/o conflict just resulting in an empty commit by now? Dunno. Removed in 9e37287 in a bigger update at this point. 🚀