semantic-release _may_not be working for our terraform modules

The `publish` step in our pipelines upon MR merge may not be working.  Example pipeline of one that simply didn't do anything: https://ops.gitlab.net/gitlab-com/gl-infra/terraform-modules/google/pubsubbeat/-/jobs/972834

I, personally, was able to reproduce this precisely.  Though another member of the team was not.  From @alejandro this appeared to work as expected on this persons workstation:

```
alejandro@MacBook-Pro-4 ~/terraform-modules/google/pubsubbeat (master) $  GITLAB_URL="https://ops.gitlab.net" GL_TOKEN="[REDACTED]" semantic-release
[3:33:58 PM] [semantic-release] › ℹ  Running semantic-release version 15.13.2
[3:33:59 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/gitlab"
[3:33:59 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[3:33:59 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[3:33:59 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/gitlab"
[3:33:59 PM] [semantic-release] › ⚠  This run was not triggered in a known CI environment, running in dry-run mode.
[3:33:59 PM] [semantic-release] › ⚠  Run automated release from branch master in dry-run mode
[3:34:04 PM] [semantic-release] › ✔  Allowed to push to the Git repository
[3:34:04 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/gitlab"
[3:34:04 PM] [semantic-release] [@semantic-release/gitlab] › ℹ  Verify GitLab authentication (https://ops.gitlab.net/api/v4)
[3:34:05 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/gitlab"
[3:34:08 PM] [semantic-release] › ℹ  Found git tag v5.3.0 associated with version 5.3.0
[3:34:08 PM] [semantic-release] › ℹ  Found 2 commits since last release
[3:34:08 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[3:34:08 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: Merge branch 'jarv/add-gke-sink' into 'master'
feat: add default sink for GKE with exclusions for application logs
See merge request gitlab-com/gl-infra/terraform-modules/google/pubsubbeat!19
[3:34:08 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[3:34:08 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: feat: add default sink for GKE with exclusions for application logs
[3:34:08 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The release type for the commit is minor
[3:34:08 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analysis of 2 commits complete: minor release
[3:34:08 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[3:34:08 PM] [semantic-release] › ℹ  The next release version is 5.4.0
[3:34:08 PM] [semantic-release] › ℹ  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[3:34:08 PM] [semantic-release] › ✔  Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[3:34:08 PM] [semantic-release] › ⚠  Skip v5.4.0 tag creation in dry-run mode
[3:34:08 PM] [semantic-release] › ⚠  Skip step "publish" of plugin "@semantic-release/gitlab" in dry-run mode
[3:34:08 PM] [semantic-release] › ✔  Published release 5.4.0
[3:34:08 PM] [semantic-release] › ℹ  Release note for version 5.4.0:
# 5.4.0 (https://ops.gitlab.net/gitlab-com/gl-infra/terraform-modules/google/pubsubbeat/compare/v5.3.0...v5.4.0) (2020-03-09)
```

In order to unblock the work being performed, @alejandro pushed up this tag.  This should be investigated to ensure other terraform modules are not also impacted.

Story points: 2.0