Rebrand to Hypermod and remove in-repo website; update docs links and package READMEs

[danieldelcore]

Motivation

• Rebrand the project from the previous CodeshiftCommunity identity to Hypermod and point users to the canonical docs and product site at https://www.hypermod.io/.
• Consolidate documentation by removing the in-repo Docusaurus website and related doc-generation scripts to rely on the external Hypermod site for official docs.
• Update package-level README files and in-transform references to avoid stale links and reduce duplicate maintenance of docs.
• Simplify the monorepo scripts by removing website-specific start/predocs steps that are no longer applicable.

Description

• Rewrote the top-level README.md to present the Hypermod product, add CLI usage examples, and link to https://www.hypermod.io/ and related resources.
• Updated package READMEs and template files (e.g. packages/cli/README.md, packages/cli-alias/README.md, packages/initializer/template/README.md, packages/utils/README.md) to replace old CodeshiftCommunity links with the Hypermod URLs and refreshed instructions/examples.
• Updated community transformer source files to point to the new docs URLs (e.g. replaced codeshiftcommunity doc links with https://www.hypermod.io/docs) without changing transformation logic.
• Removed the in-repo website and its build/asset files and scripts, including website/ content and the scripts/docs.ts doc-generation script, and removed website-related npm scripts from package.json.

Testing

• Ran yarn lint (ESLint) against the modified README and package README files and confirmed there were no new lint errors after the changes; the run completed successfully.
• Ran yarn test (Jest) for the repository test suite to ensure no regressions in unit tests and observed successful test completion.

---

Codex Task

[changeset-bot]

⚠️ No Changeset found

Latest commit: a1c226d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7414b71876

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Replace the React version example with a runnable command

The new quick-start example --packages react@18.0.0 will fail in this CLI: packages/cli/src/resolvers/npm.ts:49-60 rejects any version that is not present in config.transforms, and community/react/src/hypermod.config.js:1-16 exposes no versioned transforms for react at all (only presets). As written, a user following the first README command will get an "Unable to resolve version 18.0.0" error instead of a successful migration.

Useful? React with 👍 / 👎.