[WIP] Migrate dep to go modules

[joonas]

What this PR does / why we need it:

Go modules have become the standard way to manage dependencies across the various cluster-api (capi, capa, capz, capg, capo) projects. It seems to me that it would make sense to follow suit for the sake of standardizing.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Documentation:

Release note:

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: joonas
To complete the pull request process, please assign alvaroaleman
You can assign the PR to them by writing /assign @alvaroaleman in a comment when ready.

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

[k8s-ci-robot]

@joonas: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-cluster-api-provider-digitalocean-lint	fac8fea	link	/test pull-cluster-api-provider-digitalocean-lint

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

[joonas]

I reckon it would be best to get #138 merged in before proceeding with this one.

[cpanato]

this PR is still active? what we need to do to move forward?

[xmudrii]

@cpanato @joonas This PR depends on #138. Since we are migrating to CAPI v1alpha2 which brings significant changes to the project and includes both this PR and #138, should we close this PR or merge it anyways?

I'm planning to do a snapshot of the current master (v1alpha1) and then I think we will not accept any changes afterward. If you'd like to see gometalinter and Go modules in the v1alpha1 version, then we can merge both PRs, otherwise, I'll eventually close them.

[cpanato]

@xmudrii if we will not change this anymore maybe doe snot worth to effort to get this and the other merged and focus on that v1alpha2

[xmudrii]

Closing this PR in favor of #140.
/close

[k8s-ci-robot]

@xmudrii: Closed this PR.

In response to this:

Closing this PR in favor of #140.
/close

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/test-infra repository.