docs(release): v1.29.1 release template improvements

[BigLep]

This is for doing release process followups after executing #12470

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title conforms with contribution conventions
• Update CHANGELOG.md or signal that this change does not need it per contribution conventions
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[BigLep]

This isn't ready for review yet. I'll either work on it today or 2024-09-17. A couple of things:

1. It didn't have a step for copy/pasting in content to the GitHub release
2. There was a lot of cruft for when trying to rush out a release.

[BigLep]

@rjan90 : I think this is ready for review. I left a couple of extra comments.

I really want to get some minimal tooling that creates the release issue based on these questions:

1. Is this for a network upgrade? If so, what network version?
2. Is this a minor release?
3. Is this a patch release? If yes, what previous release are you patching?
4. Is this an emergency patch? (If yes, we can skip RC steps)

With that info, I think we can create a release issue for each of these scenarios:

1. Network upgrade / minor release
2. non-network upgrade / minor release
3. normal patch release against previous minor release
4. normal patch release against current minor release
5. emergency patch release against previous minor release
6. emergency patch release against current minor release

I've got a backlog of these type of improvements, so I don't want to commit to it yet, but I think tooling to even start creating the right set of release steps is a good beachhead towards building "lotus releaser" tooling.

[BigLep]

Merging.

Followup issue created on tooling to help with release issue creation: #12477