Gitlab CI CD components release fails due to semantic versioning with leading v

[JonasSchubert]

Gitlab is enforcing the version format for cicd components since version 16.10 using semantic versioning (without leading v).

From there docs: When tagging and [releasing new versions](https://docs.gitlab.com/ee/ci/components/#publish-a-new-release) of components to the Catalog, you must use [semantic versioning](https://semver.org/). Semantic versioning is the standard for communicating that a change is a major, minor, patch, or other kind of change..

I would suggest to add information to the docs, as this needs to be configured using the tagFormat.

[JonasSchubert]

#684 (comment)