chore(release): configure git-cliff for v0.0.1

[StringKe]

What changed

• pin git-cliff 2.13.1 through mise and add a strict Conventional Commits configuration
• generate CHANGELOG.md from repository history and set the root release version to 0.0.1
• add a tag-triggered workflow that validates annotated SemVer tags and creates GitHub release notes
• publish only the GitHub Release metadata, with no binaries, packages, containers, or custom release assets

Cloudflare Workers Builds may continue to run normally when this PR is merged to main; that existing source-deployment path is intentionally unchanged.

Validation

• actionlint -color .github/workflows/release.yml
• git diff --check
• pnpm changelog --tag v0.0.1 and clean regeneration check
• temporary annotated v0.0.1 tag dry-run with git-cliff --current --strip all
• pnpm run check
• pnpm test
• pnpm build

Release contract

After merge, an annotated v0.0.1 tag will trigger .github/workflows/release.yml. The workflow creates release notes and a GitHub Release only. It does not invoke a project build or attach custom assets.