docs: publish v2.0.0.1 release report and tagging updates

[Copilot]

Description

Prepares the v2.0.0.1 release documentation set with consistent tag/version references and a scan-friendly full release report. It also captures what is new and fixed from recent work without personal contributor attribution.

• Release reporting

  • Added a new 2.0.0.1 section to /CHANGELOG.md and /docs/changelog.md.
  • Added a full release report block to /docs/ReleaseNotes.md with:
    • release tag
    • compatibility line
    • “What’s New”
    • “What’s Fixed”
    • impact/upgrade notes

• Tag/version policy alignment

  • Updated /RELEASE_PROCESS.md to document revision-style tags (vMAJOR.MINOR.PATCH.REVISION) and refreshed command examples for v2.0.0.1.
  • Updated /VERSIONING.md to define the optional release revision segment and its meaning.

• Docs consistency

  • Updated current-version examples in getting-started install docs to v2.0.0.1.
  • Updated supported-version release date in both root and docs copies of SUPPORTED_VERSIONS.md.

git tag -a v2.0.0.1 -m "Release v2.0.0.1"

Type of Change

Please delete options that are not relevant:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings or compiler errors
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules