ci(release): Run automated release workflows outside PR context

[vishal-bala]

The existing auto release workflow is triggered by pull requests to create new releases. Apparently this corresponds to auto focusing on the specific PR that triggered the workflow to base its version bump as opposed to the entire change context since the last release.

The recommended flow is to use the auto shipit command to ensure that all of the relevant PR context is factored into the release. This PR refactors the workflow to to be triggered by pushes to main (with logic to exclude release bot commits), which should result in the expected behaviour. It also enables the workflow to be manually triggered, which should save some frustration until the process is ironed out.

---

Note

Medium Risk
Changes the automated release trigger and versioning commands, which can directly impact when/what gets released and published to PyPI. Risk is mitigated by gating on the auto:release label and skipping bot-triggered loops, but misconfiguration could block or incorrectly run releases.

Overview
Moves the release workflow from pull_request: closed to push on main (plus workflow_dispatch) and adds a gate job that finds the PR associated with the pushed commit and only proceeds when it has the auto:release label (and skips runs triggered by the release bot).

Updates the release steps to use auto shipit (instead of auto latest) for dry-run/version resolution and for creating the GitHub release, adds stricter shell error handling, and changes the version-bump commit to include [skip ci] to prevent workflow recursion.

Bumps the uv.lock revision and updates the editable package version redisvl from 0.14.0 to 0.14.1.

^{Written by Cursor Bugbot for commit 13fbe34. This will update automatically on new commits. Configure here.}

[jit-ci]

🛡️ Jit Security Scan Results

✅ No security findings were detected in this PR

---

^{Security scan by Jit}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}