Setup go-imports-organizer and organize Go imports

[coreydaley]

This is what it would look like to implement and run the go-imports-organizer on this project. Please note that I have setup the dependencies to be vendored to support not having each user install the go-imports-organizer as a standalone tool

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign rm3l for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[rm3l]

I used to run make fmt to have the code formatted, but with this, it would just verify and exit, which is kinda surprising to me. If we are just calling ./hack/verify-gofmt.sh, I would suggest renaming this Make target into verify-fmt to make the intent clearer..

I noticed that goio also formats the code as well, besides organizing the imports, right? So maybe this target could just be this instead:

fmt: imports ## Format the code using goio

Then a separate verify-fmt target that would run hack/verify-gofmt.sh.

WDYT?

[gazarenkov]

Do we need fmt verification at all?

[rm3l]

I agree fmt verification might not be necessary.

[openshift-merge-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.