🚀 Feature: Move all ESLint settings to `files`-specific blocks

[JoshuaKGoldberg]

Feature Request Checklist

• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Overview

Coming over from JoshuaKGoldberg/eslint-plugin-package-json#1265 (comment) -> eslint/eslint#20075 -> eslint/eslint#20158:

There's no longer any sense of a "primary" language for ESLint the way it used to be with JavaScript. It's now a true multi-language (JS/TS, JSON, Markdown, etc.) linter. Every group of rules has a limited set of file extensions (languages) it applies to.

This template's eslint.config.* should respect the new guidance. Right now there are still some globally applied settings:

create-typescript-app/eslint.config.js

Lines 29 to 39 in 67102a8

	eslint.configs.recommended,
	comments.recommended,
	jsdoc.configs["flat/contents-typescript-error"],
	jsdoc.configs["flat/logical-typescript-error"],
	jsdoc.configs["flat/stylistic-typescript-error"],
	jsonc.configs["flat/recommended-with-json"],
	markdown.configs.recommended,
	n.configs["flat/recommended"],
	packageJson.configs.recommended,
	perfectionist.configs["recommended-natural"],
	regexp.configs["flat/recommended"],

Those should be moved to a glob that includes JS and TS files.

Additional Info

🎁