Prepare release v2.0.1

[hel-isa]

This pull request updates the release management documentation to clarify the use of the v2 branch for consumers who want the latest compatible v2 release, and provides more detailed guidance on release flow and consumer pinning. The main changes include documentation updates on versioning strategy, consumer instructions for using the moving v2 branch, and a more explicit release pull request and tagging process.

Release versioning and consumer guidance:

• Clarified that the v2 branch can be used by consumers who want to automatically receive patch and minor updates, but exact tags (like v2.0.1) are safer for production and external onboarding. [1] [2]
• Updated instructions to recommend pinning both the workflow reference and gate_ref to the same release for predictable builds, and added a new section explaining how and when to use the moving v2 branch.

Release process improvements:

• Added a recommended pull request workflow for releases, including updating version numbers, changelogs, and validating workflows before tagging.
• Updated the release checklist to require merging a release PR into v2 before creating an annotated release tag, and clarified the steps for tagging and pushing releases.

General documentation improvements:

• Improved explanations and examples for both exact tag and moving branch strategies, making it clearer when each should be used. [1] [2]