feat: Align algorith to aquire tokens with goreleaser

[asmfreak]

This PR solves an inconsistency between provider-gitlab and hook-goreleaser when running in ci.

hook-goreleaser (and plain goreleaser) gets GITLAB_TOKEN, which is then checked against CI_JOB_TOKEN variable later in code. It then uses different API constructor calls to upload the release. It fails to find GITLAB_TOKEN, it will fail the release process.

provider-gitlab uses blindly GITLAB_TOKEN and assumes it is a valid api token. If it is missing, it uses CI_JOB_TOKEN with git repo. This fails in a situation where GITLAB_TOKEN == CI_JOB_TOKEN, since CI_JOB_TOKEN does NOT have access to the needed APIs.

This situation creates an impasse to run semantic-release with hook-goreleaser in Gitlab-CI with just a job token. This PR fixes this problem by aligning token fetching algorithms.

[christophwitzko]

@asmfreak thank you ✨

[asmfreak]

Is the workflow ok? Maybe release should not run on PRs?