feat(app-webpack): add ESLint 10 to peerDependencies

[Azelisi]

Description

@quasar/app-webpack currently declares:
"eslint": "^8.57.1 || ^9.0.0"

ESLint 10 is released. Projects on Quasar 4 + webpack cannot upgrade without ERESOLVE / --legacy-peer-deps

Motivation

• Stay on supported eslint major
• Align with @eslint/js10, eslint-plugin-vue@10, flat config (eslint.config,js)
• Avoid forcing legacy-peer-deps in CI

Environment

• @quasar/app-webpack: 4.4.5
• quasar: 2.19.x
• eslint: 9.39.x (blocked from 10)
• @eslint/js:9.x
• eslint-plugin-vue: 10.x
• Config: flat config (eslint.config.js) + eslint-webpack-plugin
• Build: Quasar CLI webpack (SPA)

Current behavior

npm intsall eslint@10 @eslint/js@10

Fails with peer dependency conflict:

peerOptional eslint@"^8.57.1 || ^9.0.0 || ^10.0.0"

quasar dev / quasar build / eslint-webpack-plugin integration work with eslint 10.

Proposed solution

1. Extend peerDependency.eslint to include ^10.0.0
2. Verify eslint-webpack-plugin + flat config with eslint 10 in a sample webpack app
3. Update linter docs if needed

Workaround (today)

npm intall -legacy-peer-deps

Not ideal for CI reproducibility.

Willing to contribute

Happy to open a PR if maintainers confirm approach (peer bump + CI test.)