Release process improvement ideas/observations from pdp v3.5.0

[BigLep]

This issue serves as a dumping ground of things that can/should be improved in the release process having gone through it as part of #304

Items beyond pdp should go in #307

After the release we'll come back through and decide which items we'll actually handle.

[BigLep]

Initial @BigLep observations from reading through the script:

Testing in foc-devnet

We llist a step for testing the upgrade steps in foc-devnet, but we also need to make sure that new functionality works in foc-devnet. That's a missing step, and was something that was holding up this release.

If the release tag must match the exact on-chain bytecode, tag the deploy commit before changelog-only closeout changes. Otherwise, tag the finalized release-notes commit and record the implementation deploy commit separately.

Why is this an "if"? The release process should make clear what path we follow and be documented as such.

Suggested release tag

Why do we say suggested? We should just state what the release tag is.

x.y.z

We have that throughout. Maybe have a step to actually fill that in to avoid confusion?

Sections in general

I think it would be good to add some hide/show toggles so can collapse

[BigLep]

@Kubuxu : I assume you'll add your dump about this process in general at and potential alternatives to foc-devnet here. There are general thoughts about foc-devnet future direction in FilOzone/foc-devnet#139