feat: enable @typescript-eslint/recommended in create-next-app --typescript

[JoshuaKGoldberg]

Fixes #37151.

This differs a bit from the discussed approach for simplicity's sake now that typescript-eslint v6 is out. I started inline comments. This takes the approach suggested in the discussion of adding a next/typescript linter preset.

Also applies a small refactor to how the strict config is found from the prompt values. Instead of a .find, I extracted out the specific value into its own function.

[ijjk]

Allow CI Workflow Run

• approve CI run for commit: b2a3ac60acc5efd9cebb0b04bef4f98c0e182326

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

[ijjk]

Allow CI Workflow Run

• approve CI run for commit: b2a3ac60acc5efd9cebb0b04bef4f98c0e182326

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

[ijjk]

Allow CI Workflow Run

• approve CI run for commit: b0783705261d140ac63e24fe86aa9cbece2e7b5f

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

[eps1lon]

I'm going to rebase this branch to get rid of the merge commits. Makes it harder to review in this state.

[eps1lon]

Let's merge this before its 1 year anniversary. Thank you for sticking with it @JoshuaKGoldberg 👍🏻

[eps1lon]

@JoshuaKGoldberg It'd be also nice as a follow-up to document how one would opt-into type-aware ESLint rules.

[JoshuaKGoldberg]

Yeah! Strong +1.

Since typescript-eslint v8 with the stabilized projectService is coming in a few months, my suggestion would be to procrastinate until then. That way we can use the nice:

{
  "extends": ["next/core-web-vitals", "next/typescript",
+  "plugin:@typescript-eslint/recommended-type-checked" // (or similar)
  ],
+ "parserOptions": {
+   "projectService": true
+ }
}