Move GitLab release to its own job

What does this MR do?

Move GitLab release to its own job

Why was this MR needed?

When we want to do a security release, we have to create the tag in a private fork gitlab-org/security/gitlab-runner. When we create the tag in the private fork we don't want it to create a GitLab release as soon as the pipeline finishes until the vulnerability is announced publicly.

Move the release create to its own job, have it create the release if the pipeline comes from gitlab-org/gitlab-runner and then manual when pipeline comes from gitlab-org/security/gitlab-runner.

What's the best way to test this MR?

Example pipelines for https://gitlab.com/steveazz-playground/security-private/-/blob/ae154fdb7e354c8272d8f52d8fe8813edcc47d54/.gitlab-ci.yml

• Automatically: https://gitlab.com/steveazz-playground/security-public/-/pipelines?page=1&scope=all&ref=v0.0.6
• Manual: https://gitlab.com/steveazz-playground/security-private/-/pipelines?page=1&scope=all&ref=v0.0.6

What are the relevant issue numbers?

reference #21301 (comment 384403141)