./gradlew check fails on a clean clone of Beam

[damccorm]

Our contribution guide directs new contributors to run ./gradlew check after getting their environment setup, but its actually quite hard to do this.

• There are a number of tests run under the :test task that actually access external services, and/or require some authentication to be setup (BEAM-11363)
• There is often an issue with :sdk:go:goVet that looks like BEAM-4422. It seems flaky, perhaps its being broken by another task? Described some investigation here

Imported from Jira BEAM-11402. Original Jira may contain additional context.
Reported by: bhulette.