Normalize release tags to vX.X.X format for python-semantic-release

[farhan]

Purpose

Normalize the release/version tag format to vX.X.X (with the v prefix) across the repos listed below.

Why this is needed

As we convert repos to python-semantic-release (PSR), PSR looks at existing tags to determine the current version and compute the next one. PSR expects tags in the form v#.#.#, but several repos currently tag versions without the v prefix (e.g. 4.0.0 instead of v4.0.0).

When the v prefix is missing, PSR fails to recognize the latest version and wrongly starts a fresh 0.1.0 release instead of bumping from the real current version. Re-tagging these repos to the vX.X.X format ensures PSR picks up the correct history and versions the next release accurately.

Original context from the Feanil:

Something to watch out for as we convert things to python semantic release — to find old versions to figure out what the next version should be. PSR looks for tags like v#.#.#, but in many of our repos we don't currently have the v prefix on version tags, so in those cases it wrongly tags a new 0.1.0 version.

Slack message

Repos to fix

These repos have their latest release/version tag without the v prefix:

• acid-block — 0.4.0
• opaque-keys — 4.0.0
• openedx-webhooks — release-2023-11-27
• ccx-keys — 2.0.2
• web-fragments — 4.0.0
• edx-enterprise-data — 10.22.14
• openedx-chem — 2.0.0
• xblock-free-text-response — release/v5.1.0
• enmerkar-underscore — 2.4.1
• pytest-repo-health — 4.0.0
• license-manager — release/verawood.1
• taxonomy-connector — 4.0.0
• olxcleaner — 0.3.0
• codejail-includes — 2.0.0
• xblock-skill-tagging — 1.0.0
• openedx-ledger — 2.0.0
• edx-enterprise-subsidy-client — 2.2.2
• enterprise-integrated-channels — 0.1.69

Parent: #506