🚀 Feature: Don't include n/no-missing-import allowModules if README.md doesn't violate it

[JoshuaKGoldberg]

Bug Report 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

Right now, the generated ESLint config for repos always configures n/no-missing-import's allowModules to include options.repository:

create-typescript-app/src/steps/writing/creation/createESLintConfig.ts

Lines 101 to 106 in aaf2d65

	rules: {
	"n/no-missing-import": [
	"error",
	{ allowModules: ["${options.repository}"] },
	],
	},

This is necessary because created repos by default have a Getting Started / Usage section like:

import { greet } from "create-typescript-app";

But, in the create Blocks version, that's not always true. Repositories may customize that section. This repo does it and removes the offending code altogether.

So, I'd like to have the ESLint Block only include that allowModules setting if options.usage actually includes code that would make it useful.

Additional Info

I don't plan on adding this to the legacy engine, just create blocks.

Prototyped in #1839.

💖