Patch release pipeline: Automate versions creation

Context

After the patch release packages are published, the release managers create versions manually on version.gitlab.com.

• Create <version> version on version.gitlab.com. Be sure to mark it as a security release. From the Security Release dropdown choose Non Critical. After it is created, the Vulnerability Type column should indicate No for the new version.

This issue is to automate that process by implementing a set of jobs for the patch (security) release pipeline.

Proposal

• There should be one job per version
• There's an API for version creation on https://gitlab.com/gitlab-org/gitlab-services/version.gitlab.com/-/tree/main/lib/api?ref_type=heads that we can leverage
• There's a similar monthly release automation issue: #20196 (closed) and MR. If there are common implementation, let's refactor it to work with patch releases as well
• Follow guidelines for the release pipelines in https://gitlab.com/gitlab-org/release-tools/-/blob/master/doc/release-pipelines.md

Exit Criteria

• Release managers can use the patch release pipeline to create versions
• The release task issue is updated to use the patch release pipeline to create versions