fix: Corrects release branch naming

[danehans]

• Fixes the release branching naming
• Adds add'l context for release steps

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danehans

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [danehans]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for gateway-api-inference-extension ready!

Name	Link
🔨 Latest commit	7d232c0
🔍 Latest deploy log	https://app.netlify.com/sites/gateway-api-inference-extension/deploys/67a51bd1f7eb6c0008a21dfc
😎 Deploy Preview	https://deploy-preview-299--gateway-api-inference-extension.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[k8s-ci-robot]

@danehans: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-gateway-api-inference-extension-test-unit-main	7d232c0	link	true	/test pull-gateway-api-inference-extension-test-unit-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[kfswain]

/lgtm
/hold
This LGTM.
But just an FYI that this was developed on the upstream repo. Can we keep the upstream branches to tagging (and other things that require using the upstream) so there are no 'whoopsie' moments that could bite us?

Just holding to bring attention to the comment, feel free to ack/unhold at your leisure. Thanks again for this!

[ahg-g]

Is this PR still relevant?

[k8s-ci-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[danehans]

But just an FYI that this was developed on the upstream repo. Can we keep the upstream branches to tagging (and other things that require using the upstream) so there are no 'whoopsie' moments that could bite us?

Ack. I was trying to recreate it as close to upstream as possible but I agree that this should be done using downstream.

[danehans]

Closing in favor of #333