This change set is a workaround for
https://gitlab.com/gitlab-org/gitlab/-/issues/438275.
It implements an additional release step that "hard codes" the component
version to release in the component templates. This is ugly, but hides
complexity from the component user.

This change set maybe a breaking change to component users that rely on
the default being `latest`. For example, a config like:

    include:
      - component: $CI_SERVER_FQDN/components/opentofu/full-pipeline@~latest
        inputs:
          opentofu_version: <OPENTOFU_VERSION>

would break, because the component `version` value is no longer
`latest`, but no refers to the actual version from of `~latest`.
Since, using `~latest` is "discouraged" anyways, we'll still introduce
this breaking change. Users of `~latest` should just specify `version:
latest` in their `inputs`.

Changelog: changed