Apply go formatter changes on ./gradlew build

[Ardagan]

These are automatically generated changes when ./gradlew build --continue is executed. I'm not sure whether all of those are caused by gofmt task or some others involved as well.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang	SDK	Apex	Dataflow	Flink	Gearpump	Samza	Spark
Go		---	---	---	---	---	---
Java
Python		---			---	---	---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

[Ardagan]

R: @lostluck (Go sdk contributor)
CC: @pabloem (committer)

[Ardagan]

R: @youngoli (go sdk contributor)

[youngoli]

Changes are all legit.

I'm surprised these weren't caught before. I would have assumed that Go SDK commits had a format checker like PyLint for Python or Spotless for Java that would've caught these when they were first being committed. Thanks for fixing these Mikhail.

[pabloem]

Happy to merge - can you add a JIRA for this?

[Ardagan]

@youngoli
I believe most people just build project they are working on atm. I find it convenient to sometimes build whole project (I do -X test and some other stuff though).

@pabloem
This is merely applying formatter. I believe that creating jira for such minor changes will only create more clutter. Do you think we should move such discussion to dev-list?

[pabloem]

That's fair enough. We also don't want to pollute JIRA too much, and the merge commit leads to the PR, so it's reasonable. Thanks!