docs(readme): refresh version/SHA table for the latest releases

[MAfarrag]

Description

Refresh the README's version references to the releases just cut at 38c1110 (main tip). All six actions were
tagged: pip, uv, pixi, and pypi-release/mkdocs got patch bumps for the script-injection hardening (#28); mkdocs
also carries the mike-push retry (#25); release/github got a minor bump for the changelog-detection fix (#30) plus
the hardening.

Three spots updated, verified against the pushed tags (every rolling v1 resolves to
38c111084f99d5ff5f4a1e63bedce48fe33a10c0):

• Versioning code block — pip v1.1.1, uv v1.2.1, pixi v1.2.1, mkdocs v1.3.1, github-release v1.5.0,
  pypi-release v1.0.3.
• Pinning examples — exact-patch uv/v1.2.1 and the commit-SHA example updated to 38c1110….
• "Current versions and rolling-v1 commit SHAs" table — Latest version + Commit SHA columns.

Docs only; no action code changes.

Issues

• No issue — routine post-release README refresh.

Type of change

• 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)
• This change requires a documentation update

How Has This Been Tested?

• Cross-checked every rolling-v1 tag with git rev-parse <tag>^{commit} — all resolve to 38c1110, matching
  the SHAs written into the table.
• Grepped the README for stale version/SHA strings; the only remaining mkdocs/v1.1.0/v1.2.0 mentions are
  historical "feature landed in X" notes and are intentionally left as-is.

Checklist:

• updated version number in pyproject.toml. (n/a — no package version; actions use namespaced tags)
• added changes to History.rst. (n/a — repo has no History.rst)
• updated the latest version in README file.
• I have added tests that prove my fix is effective or that my feature works. (n/a — docs only)
• New and existing unit tests pass locally with my changes. (n/a — docs only)
• documentation are updated.