🐛 Bug: Don't infer --description if it's the same as create-typescript-app's

[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, --description defaults to the description in a package.json file:

create-typescript-app/src/shared/options/createOptionDefaults/index.ts

Line 34 in dd4fc29

description: async () => (await packageData()).description,

...but, in a repository newly created from the template, that description will likely be the default create-typescript-app one:

┌  ✨ Welcome to create-typescript-app 1.57.8! ✨
│
│  ⚠️ This template is early stage, opinionated, and not endorsed by the TypeScript team. ⚠️
│  ⚠️ If any tooling it sets displeases you, you can always remove that portion manually. ⚠️
│
◇  What organization or user will the repository be under?
│  JoshuaKGoldberg
│
◇  What will the kebab-case name of the repository be?
│  github-notifications-prune
│
◇  ✅ Passed checking GitHub authentication.
│
◆  How would you describe the new package?
│  Quickstart-friendly TypeScript template with comprehensive, configurable, opinionated tooling. 💝
└

If the package.json description is the same default description as create-typescript-app's as seen in that code block, then it's not likely a good suggestion for a newly created package. Let's have the logic also check the GitHub repository's About as second thing:

...and don't include a suggestion if both are the default description.

Additional Info

No response

[JoshuaKGoldberg]

On second thought, there's not really much use in checking the repository's About. Most use cases don't involve setting that before running the script. I think I'd rather just default to undefined and have the CLI prompt the user.