Bump eslint from 9.39.4 to 10.3.0

[ggtlvkma356]

Supersede #638.

Dependencies to @eslint/js was removed from eslint. See eslint/eslint#20539.

[inthewaves]

We should update README.md as it says Node.js 20+, but they removed support for Node.js < v20.19: https://eslint.org/docs/latest/use/migrate-to-10.0.0#drop-old-node

ESLint is officially dropping support for these versions of Node.js starting with ESLint v10.0.0. ESLint now supports the following versions of Node.js:

• Node.js v20.19.0 and above
• Node.js v22.13.0 and above
• Node.js v24 and above

To address: Make sure you upgrade to at least Node.js v20.19.0 when using ESLint v10.0.0.

[inthewaves]

Actually pdfjs seems to want higher Node.js too (though haven't seen issues)l, this is from the CI run

> Task :app:npmSetup
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: 'pdfjs-dist@5.7.284',
npm warn EBADENGINE   required: { node: '>=22.13.0 || >=24' },
npm warn EBADENGINE   current: { node: 'v20.20.2', npm: '10.8.2' }
npm warn EBADENGINE }

[ggtlvkma356]

Actually pdfjs seems to want higher Node.js too (though haven't seen issues)l, this is from the CI run

> Task :app:npmSetup
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: 'pdfjs-dist@5.7.284',
npm warn EBADENGINE   required: { node: '>=22.13.0 || >=24' },
npm warn EBADENGINE   current: { node: 'v20.20.2', npm: '10.8.2' }
npm warn EBADENGINE }

That is likely because of the default version used by setup-node. I can change the workflow to use a higher version.