Update CLI config-template doc URLs for specsplugin.com migration

[nathanacurtis]

Problem

Running specs init generates a config file whose comments link to the docs site at directededges.github.io/specs/config/…. Those links break when the docs site moves to https://www.specsplugin.com/, and they already point at a /config/ path that doesn't exist on the site (that content lives under /settings/).

Solution

Update the documentation URLs embedded in the generated config templates to the new domain and correct path, so a freshly generated config links users to live pages.

Acceptance criteria

• specs init output links point to https://www.specsplugin.com/settings/… (docs root → …/settings/)
• No generated link resolves to a 404
• Docs-site examples of the generated config show the same corrected URLs

Notes

• Source: packages/cli/src/Config/ConfigTemplates.ts (~10 URLs of form …github.io/specs/config/…).
• Path reconciliation /config/ → /settings/ (e.g. /settings/keys/, /layout/, /tokens/, /color/, /subcomponents/, /variant-depth/, /details/).
• Update asserting tests: packages/cli/tests/unit/config/ConfigTemplates.test.ts, packages/cli/tests/unit/commands/InitCommand.test.ts.
• Mirror the same change in the two # See: / # Documentation: lines in site/src/content/docs/cli/commands/init.md.
• Released CLI artifact — lands in a CLI release, kept separate from the site-migration branch (project 015). Don't start until the domain switch is scheduled.

Related: project 015 site migration (branch chore/site-migration).