ci(lint): Take no inline ESLint configuration
Every ESLint config sets noInlineConfig, so a comment can neither turn a rule
off nor reconfigure one: // eslint-disable-next-line @typescript-eslint/no-explicit-any above an any used to pass the lint and
now leaves the error standing, with a warning that the comment does nothing.
The dashboard's own lint run takes --max-warnings 0 as the other two runs of
scripts/ci/lint-web.sh do, so that warning fails it as well.
The eight comments that turned react-hooks rules off went in the commit
before; the image tier's /* exported IT */ becomes the config's
varsIgnorePattern for the global its pages call. A planted disable comment
above an any in the web core, in the dashboard and in tests/tools fails each
run.