ci/gomod: added CI validation to prevent changing patch version of Go from non-zero

[mtulio]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Introduce the step to validate if the go.mod is in conformance with Kubernetes project standard by using the patch version from the build env (ending with .0, x.y.0).

This PR presents two options:

• 1. local only test using github actions
• 2. shared practice using cluster-api standardization script (preferred)

Please leave a comment with your thoughts of which option would be ok to follow the practice by this project.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

[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 mmerkes for approval. For more information see the 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

[k8s-ci-robot]

This issue is currently awaiting triage.

If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[mtulio]

/test all

[elmiko]

this makes sense to me

[mtulio]

I just added one more option to validate 'go.mod dotzero' using cluster-api practice, which would be preferred as shares practices from other kube projects (suggested by @damdo, TY). PTAL, would love to hear thoughts which path to go.

[mtulio]

/test pull-cloud-provider-aws-check

[damdo]

We should be able to drop this in favour of if the make check. As its passing as a presubmit should already be mandatory for PRs right?

[JoelSpeed]

Being able to run the same checks locally would be very helpful, and then running that same check in an action gives us continual testing of that