Migrate ESLint targets to @nx/eslint/plugin inference

[tbinna]

Problem

Nx 23 warns that the @nx/eslint:lint executor is deprecated and will be removed in Nx 24. The workspace still declares explicit lint executor targets for nx-forge and docs-tools.

The application generator also defaults to explicit-target generation through addPlugin: false. Generator tests repeatedly exercise that path, producing many copies of the same deprecation warning. This leaves both the workspace and generated Forge applications on a target model that Nx is removing.

Scope

• Configure @nx/eslint/plugin inference for the workspace.
• Convert the nx-forge and docs-tools lint targets.
• Update the application generator so its normal output uses inferred ESLint targets.
• Decide and test the compatibility behavior for callers that explicitly request addPlugin: false.
• Adapt generator tests so they verify the intended inferred output without hiding unexpected warnings.
• Preserve the existing flat ESLint configuration and lint semantics.

Acceptance criteria

• Resolved workspace configuration no longer uses @nx/eslint:lint.
• Generated Forge applications use @nx/eslint/plugin inference by default.
• The public lint target remains available with equivalent behavior.
• Existing lint inputs, output-file behavior where applicable, and Nx caching remain correct.
• Generator tests cover inferred targets and any intentionally supported legacy mode.
• Test and CI logs no longer contain the ESLint executor deprecation warning.
• Relevant format, lint, build, unit, and generator tests pass.

Reference

• https://nx.dev/docs/guides/tasks--caching/convert-to-inferred

[tbinna]

Closing #215 and putting this migration on hold for now.

We compared the implementation with both the Nx 23.0.1 source used by this repository and current upstream Nx master. Although the Nx workspace itself uses @nx/eslint/plugin inference, the Node application generator—and most other first-party application generators—still defaults to addPlugin: false and explicit targets.

Implementing ESLint-only inference here would require nx-forge-specific option plumbing for ESLint, Jest, and Webpack without an upstream reference design. We would prefer to revisit this issue once Nx updates its own generators, so we can follow the upstream compatibility behavior closely rather than maintaining a divergent implementation.