[WIP] Add support for hotfixes with semver

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

---

This section details on the original issue you should resolve

<issue_title>[Feature]: Hotfix Support</issue_title>
<issue_description>### Before filing

• I searched existing issues and did not find a duplicate.

Area

Documentation

Problem or need

We need to support hotfixes, with semver, for example when we deploy 0.0.27 and we continue deploying 0.0.28, we need to hotfix 0.0.27-hotfix.1 in this format.

What we will do, is branch off the tag 0.0.27 to new branch, and we run the cargo xtask version 0.0.27-hotfix.1 and commit it in that branch. Then we will run the pipeline in Azure DevOps ESRP on that branch and it should properly publish the package.

It would be great if we have a tool in cargo xtask hotfix <sha> <last-tag> for example if we do cargo xtask hotfix 121323232414124 0.0.26 it will cherry-pick that commit sha to each tag between HEAD and those versions, and for each version it will publish that branch. A tool to manange hot fixes.

So we can have multiple hotfixes 0.0.27-hotfix.1 0.0.27-hotfix.2 , the number after the hotfix.<num> gets incremented

Who would benefit?

No response

Desired outcome

No response

Concrete example

No response

Constraints

No response

Alternatives or workarounds

No response</issue_description>

• Closes [Feature]: Hotfix Support #500

<agent_instructions>Make sure the versions would work with the hotfix suffix</agent_instructions>

Comments on the Issue (you are Copilot in this section)

• Fixes [Feature]: Hotfix Support #500