Fix release-plz PR creation by enabling credential persistence

[Copilot]

The release-plz-pr workflow job was failing with a 403 error when attempting to create pull requests. The job inherited persist-credentials: false from a YAML anchor, preventing the GITHUB_TOKEN from being available to the release-plz action.

Changes

• .github/workflows/release.yml: Replace YAML anchor reference in release-plz-pr job with explicit checkout step that allows credential persistence (default behavior)

# Before: inherits persist-credentials: false from anchor
steps:
  - *checkout  # includes persist-credentials: false
  - *install-rust

# After: explicit checkout with default credential persistence
steps:
  - name: Checkout repository
    uses: actions/checkout@v4
    with:
      fetch-depth: 0
  - *install-rust

The release-plz job retains persist-credentials: false as it only performs releases and doesn't require token persistence.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR fixes the release-plz-pr workflow job failing with 403s when creating pull requests by ensuring the job has access to a persisted GITHUB_TOKEN. It does so by overriding the shared checkout configuration that previously disabled credential persistence.

Changes:

• Update the release-plz-pr job in .github/workflows/release.yml to use an explicit actions/checkout@v4 step with fetch-depth: 0 and default credential persistence.
• Leave the main release-plz job behavior unchanged so it still uses persist-credentials: false.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.