ci: migrate release pipeline onto the reusable homeboy-action release workflow

[chubes4]

What

Replaces the hand-rolled ~200-line release.yml with a ~40-line caller of Extra-Chill/homeboy-action/.github/workflows/release.yml@v2 (shipped in homeboy-action v2.16.1 via #473 + #474).

Before / after

Before: this repo re-implemented, job by job — releasable-commit grep, dry-run version prediction, actions/cache failed-SHA marker across check / record-failure / clear-failure, app-token generation, persist-credentials: false checkout, the release call.

After:

jobs:
  release:
    uses: Extra-Chill/homeboy-action/.github/workflows/release.yml@v2
    with:
      dry-run: ${{ inputs.dry-run || false }}
      args: '--setting database_type=mysql --setting wp_codebox_phpunit_config=/wordpress/wp-content/plugins/data-machine/phpunit.xml.dist'
    secrets: inherit

Behavior

Unchanged: triggers (push main + dispatch with dry-run), permissions, WordPress extension args, skip on release: head commits.

Inherited improvements this repo did not have: failed-SHA marker keyed on tooling-identity so a fixed binary/extension self-heals a blocked SHA, and manual dispatch always bypasses the marker (homeboy-action#257).

Added: concurrency: { group: release, cancel-in-progress: false } so two fast merges queue instead of racing a tag.

This is the first real run of release.yml@v2

The reusable workflow passes homeboy-action's shape gates but has not executed end to end anywhere. After merging, dispatch this workflow with dry-run: true before any releasable commit lands to prove the check job (version prediction + tooling-identity) works in a consumer context. This PR itself is ci: and will not trigger a release.

Deploy

Releases are not auto-deployed by this change. Network deploy is moving to a single push-based workflow in extrachill-network (tracked there); until that lands, deploys stay manual.

Refs Extra-Chill/homeboy-action#472

---

AI-generated by Extra Chill Bot via Kimaki; reviewed by nobody yet.