chore: remove payload-plugin-content-releases from main

[owarpero]

Summary

Removes the in-development `@focus-reactive/payload-plugin-content-releases` package from main while parking the full implementation in PR #7 (`feature/releases-plugin`).

The plugin work is not lost — every commit, file, test, and the screenshots from the QA pass are preserved on `feature/releases-plugin`. Re-introducing the plugin is a matter of merging that PR (or rebasing it onto the new main).

Removed from `main`

• `packages/payload-plugin-content-releases/` — entire package directory.
• `apps/dev/package.json` — workspace dependency entry.
• `apps/dev/src/payload.config.ts` — import + plugin entry in `plugins` array.
• `apps/dev/src/app/(payload)/admin/importMap.js` — regenerated via `bun run generate:importmap` (auto-removes orphan plugin entries).
• `apps/dev/src/payload-types.ts` — regenerated via `bun run generate:types` (auto-removes `Release` / `ReleaseItem` types).
• `package.json` — restored the simple `multi-semantic-release --ignore-private-packages` script. The `--ignore-packages @focus-reactive/payload-plugin-content-releases` workaround introduced in be1b287 is no longer needed once the package itself is gone.
• `bun.lock` — refreshed via `bun install`.

Intentionally not touched

• `apps/dev/dev.db` — local SQLite state. Orphan `releases` / `release-items` tables are harmless and only affect each developer's own machine. Each dev can drop those tables manually if they care.
• `docs/plans/2026-03-26-content-releases-*.md` — historical design documents kept as project history.

Verification

• `bun install` clean.
• `bun run build` — all 4 remaining published packages (`payload-plugin-ab`, `payload-plugin-comments`, `payload-plugin-presets`, `payload-plugin-scheduling`) build cleanly.
• `bun run generate:types` and `bun run generate:importmap` both run and emit zero plugin references.
• `grep -r "payload-plugin-content-releases" --include='.ts' --include='.tsx' --include='.json' --include='.js' --include='.mjs' --include='.yml' .` (excluding `docs/` and `node_modules/`) → 0 hits.

apps/dev's own next-build still has unrelated pre-existing libsql / @eslint/eslintrc resolution issues — they exist on main today, not introduced or fixed by this PR.

How to bring the plugin back later

Either:

1. Merge PR feat(content-releases): finalize plugin #7 once the plugin is ready to ship — the merge will re-introduce `packages/payload-plugin-content-releases/` and re-add all the apps/dev wiring, on top of all UX improvements made there.
2. Or cherry-pick / rebase `feature/releases-plugin` onto the new main if you want to land it as a fresh branch.

🤖 Generated with Claude Code

[github-actions]

🎉 This PR is included in version 0.10.6 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.6.2 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.2.0 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 2.4.1 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀