chore: update cspell config

[RebeccaStevens]

PR Checklist

• Addresses an existing open issue: fixes #000
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

Updates cspell config to new recommended style.

[github-actions]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. We are closing this pull request for now but you can update the pull request description and reopen the pull request.
The check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (f12728a) 80.22% compared to head (5b0893f) 80.22%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #342   +/-   ##
=======================================
  Coverage   80.22%   80.22%           
=======================================
  Files          35       35           
  Lines        6406     6406           
  Branches      360      360           
=======================================
  Hits         5139     5139           
  Misses       1267     1267           

Flag	Coverage Δ
4.3.5	80.00% <ø> (ø)
4.6.4	80.03% <ø> (ø)
4.9.5	80.03% <ø> (ø)
latest	80.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[JoshuaKGoldberg]

new recommended style.

I don't love having two config files now 😕 where is this new style recommended from?

[JoshuaKGoldberg]

From my perspective this is a net negative. I'd like to reduce the number of config files in projects (https://github.com/JoshuaKGoldberg/create-typescript-app/milestone/3).

[RebeccaStevens]

We could put a lot of the config files in a sub config directory. Would that work or do just want to reduce file count?
A lot of configs can be put into package.json but I don't like polluting that file with configs.

[JoshuaKGoldberg]

Yeah IMO having as few files as possible is a good goal. Splitting into sub-directories still means there's more stuff to parse through.

Aside: IIRC there is/was a movement to make .config a standard, but since not every tool supports it I think it'd be potentially more confusing to folks to have two places to put configs...