[3.5] Backport release script fixes

[jmhbnz]

This pull request:

• Backports b82f882 to release-3.5 to prevent issues with git remotes when the script attempts to push tags.
• Partially backports 396efd9#diff-1bba00e5aca52286a667c09eff92ba2ca8e3ca77e0d31b0599cc829ab0173389 to release-3.5 to ensure all key etcd branches release-3.4, release-3.5 and main all use the same name for the release script which aligns with our release documentation.

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[serathius]

If you are trying to update the commit history to show file fork in code review, I can say I tried and it doesn't work on github.

[jmhbnz]

If you are trying to update the commit history to show file fork in code review, I can say I tried and it doesn't work on github.

I was hoping github would show the file as renamed rather than just updated but I don't think it will work that way yeah.

All good - ready for review now.

cc additional attendees of 3.5.13 release call @ahrtr, @spzala

[ahrtr]

BTW, I think we should release 3.5.14 and 3.4.32 based on the release criteria. @jmhbnz @spzala

Will work together with @spzala to get 3.4.32 released.

[spzala]

Thanks @jmhbnz