Release process retrospective 0.10.0

[dannycjones]

Opening this issue to track issues faced during 0.10.0 release process, and track improvements.

Release guide: https://rust.iceberg.apache.org/release

Issues faced:

Issue	Manual Resolution	Long-Term Resolution
RC1 failed due to a regression found concurrently with voting	PR merged and taken into RC2	N/A
RC2 failed as the tag did not match the archive contents (full workflow not retries)	RC3 cut	TODO: Review release guide content to emphasize when a new RC needs to be cut
Churn between release candidates as new commits were brought in from main	Eventually cut a branch for 0.10.0	TODO: Formalize process for cutting a release branch (like 0.10.x)
RC3 failed as LICENSE and NOTICE files were missing from individual crate archives, reported against 0.9.1 concurrently with voting	Updated in source: #2830	TODO: Add validation to CI and/or release verification scripts
Final release steps must be owned by PMC member, not committer.	Handed over to @blackmwk	TODO: Update release runbook to clarify this
Trusted publishing failed for Python packages	TBD	TODO: Update release guide to mention this limitation and steps that need to be taken.
Trusted publishing fails for new crates (#2863)	New crates manually published by @blackmwk	TODO: Update release guide to mention this limitation and steps that need to be taken.
Draft GitHub release for 0.10.0 was missing when it came time to publish	Created by @blackmwk	TBD, might just be a miss following the guide
Final announcement e-mail must be owned by Iceberg committer, and must not be text/html	None	TODO: Clarify who is responsible for the e-mail in the release guide
GH Issue template is not updated as part of release process	Opened PR: #2826	TODO: Add to release guide, or use freeform text input instead

[dannycjones]

I've opened this for tracking. I'm happy of course for anyone to pick up tasks here.

I'll be away from work a bit over the next month, so I'll be chipping away at some of these slowly.