storage: 26.4 branch checklist

Checklist for things that need to be done when a release branch is cut (And always refer to wiki for latest instructions https://cockroachlabs.atlassian.net/wiki/spaces/STOR/pages/4672553027/Pebble+Releases)

- [] [Pebble repo] Cut `crl-release-xy.z` branch in Pebble at the same SHA that the `release-xy.z` branch is using
- [] [Pebble repo] Add `crl-release-xy.z` to the nightly workflow (in Pebble actions).
* Copy the last `release-ab.c.yaml` file to `release-xy.z.yaml`
* Update title and `BRANCH`
* Update the `go_version` fields if necessary (they should match the Go that is used on the CRDB branch)
* Example PR (26.2): https://github.com/cockroachdb/pebble/pull/5863
- [] [CRDB repo] Update `bump-pebble.sh` and teamcity scripts on branch `release-xy.z` to use `crl-release-xy.z` instead of `master`
* Example PR (26.2): #166763
- [] [CRDB repo] Clone this issue for the next release
* ticket for next release: TODO

Jira issue: CRDB-62080

Jira issue: CRDB-65895

Start with the linked Pebble Releases wiki instructions, then inspect the Pebble nightly workflow and the CRDB bump-pebble.sh and TeamCity scripts on the release branch. Use the 26.2 example PRs as references, verify every checklist item for the 26.4 branch, and fill in the next-release ticket before cloning the issue.

Written by the indexing model from the issue text.