fix: multi instance release

Background

jsonnet-tool is used for multiple projects, both hosted on GitLab.com and ops.GitLab.net. ops.GitLab.net is used to operate GitLab.com, so we can't have any dependecies between them. In https://ops.gitlab.net/gitlab-com/gitlab-com-infrastructure/-/merge_requests/2896 we need to use the jsonnet-tool image inside of our pipeline, which is why we need to have the image inside of ops.GitLab.net

Solution

Update goreleaesr and semantic-release so it doesn't try to tag,push containers on just GitLab.com but use predefined environment variable to know to which GitLab instance to push binaries/images.

Testing

• GitLab.com
  • main: https://gitlab.com/steveazz/jsonnet-tool/-/pipelines/368489410
  • tag: https://gitlab.com/steveazz/jsonnet-tool/-/pipelines/368491758
• ops.GitLab.net
  • main: https://ops.gitlab.net/steveazz/jsonnet-tool/-/pipelines/785677
  • tag: https://ops.gitlab.net/steveazz/jsonnet-tool/-/pipelines/785682