chore(ci): add version number normalization to docs publishing

[dreamorosi]

Description of your changes

As described in the linked issue, the docs publishing workflow was creating version numbers that contained a v prefix, which is not in line with the rest of the versions used across docs.

This PR introduces an additional step to the reusable-publish-docs workflow to normalize the version number and remove the prefix when previous. This way docs will always be published under the correct version/convention.

Once merged this issue closes #1421.

Related issues, RFCs

Issue number: #1421

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding changes to the examples
• My changes generate no new warnings
• The code coverage hasn't decreased
• I have added tests that prove my change is effective and works
• New and existing unit tests pass locally and in Github Actions
• Any dependent changes have been merged and published
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.