chore: make the release pipeline prerelease-aware, add 3.0.0-beta-2 n…

…otes

npm publish defaults to the `latest` dist-tag and does not special-case
semver prereleases. Publishing 3.0.0-beta-N without an explicit --tag
served the beta to every `npx foifi` and to /5:update, which runs
`npx foifi@latest --upgrade`. That is what forced the walk-back after
3.0.0-beta-1 (reset version to 2.0.6, remove notes, repair dist-tags).

- publish.yml derives dist_tag and prerelease from the version: a
  hyphenated version publishes to `beta` and marks the GitHub Release
  as a prerelease; everything else keeps publishing to `latest`
- both publishes (foifi and the legacy 5-phase-workflow) pass --tag
- a prerelease no longer pushes its version bump to main; package.json
  is still updated locally so npm publish ships the right version
- release.md passes --prerelease for hyphenated versions. It creates
  the GitHub Release before the workflow does, so the workflow's own
  prerelease flag never applies

Also adds the 3.0.0-beta-2 release notes covering the two wrap commits
and their breaking changes.

chore: remove 3.0.0-beta-1 from release notes

Merge pull request #10

feat/workflow-tool-implement

Update Release Notes 2.0.6

Update Release Notes 2.0.5

Update Release Notes 2.0.4

Update Release Notes 2.0.3

Update Release Notes 2.0.2

Update Release Notes 2.0.1

Remove unnecessary npm install step from publish workflow