ci: improve release workflow automation

[roottool]

Description

This PR improves the release workflow by introducing a two-step release process:

1. Prepare Release PR Workflow - Automates version bumping and release PR creation
2. Simplified Publish Workflow - Converts from tag-based to manual workflow_dispatch trigger

Changes

• Add prepare-release-pr.yml workflow for automated release preparation
  • Supports semantic versioning selection (patch/minor/major)
  • Automatically bumps version and creates release PR
  • Auto-assigns PR and adds "ignore for release" label
• Simplify publish.yml workflow
  • Change from tag-based trigger to manual workflow_dispatch
  • Remove separate validation job (validation now inline)
  • Create git tag after successful npm publish
  • Use gh CLI for release creation instead of action
• Update release changelog configuration
  • Reorder categories (Breaking Changes first)
  • Add alternative label names for better flexibility

Boundary Checklist (Required)

• No interpretation

  • Key names are treated as opaque strings
  • No structural inference ([], ., brackets, paths, etc.)

• No silent behavior

  • No merging, overwriting, auto-fixing, or implicit resolution
  • All boundary violations are reported explicitly

• Boundary respected

  • No validation, coercion, schema, framework conventions, or business logic

📘 Boundary rules & non-goals:
https://github.com/roottool/safe-formdata/blob/main/AGENTS.md

Type of Change

• Bug fix
• Security fix
• Documentation
• Refactoring (no behavior change)
• Tests
• Tooling / CI

Testing

The new workflows will be tested in the next release cycle:

1. Run "Prepare Release PR" workflow to create a release PR
2. Merge the release PR
3. Run "Publish" workflow to publish to npm and create GitHub release

---

🤖 Generated with Claude Code

Co-Authored-By: Claude [email protected]

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (cb38a4b) to head (fb58c3a).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #28   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           22        22           
  Branches         6         6           
=========================================
  Hits            22        22           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.