RHOAIENG-8554: Add static-checks GitHub action for go code

[jiridanek]

https://issues.redhat.com/browse/RHOAIENG-8554

Description

Adds static-checks GitHub action for go code

How Has This Been Tested?

See the GHA run

Merge criteria:

• The commits are squashed in a cohesive manner and have meaningful messages.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

[atheo89]

I put a small suggestion.

[jstourac]

LGTM, thanks!

The question for the vulnerability check - it is failing right now, do we intend to merge this as is even it's failing? I guess the answer is yes?

[jiridanek]

The question for the vulnerability check - it is failing right now, do we intend to merge this as is even it's failing? I guess the answer is yes?

I'd merge it failing, and then would try to quickly fix it. It should not be too hard, I hope.

The govulncheck is less sensitive than snyk, it analyzes whether the vulnerable function is called and only reports of that is the case. So it should not report too many problems.

If I manage to improve the integration test to actually spawn a notebook in the clusters then we would be able to merge dependency updates when the test passes. No other manual work would be necessary to verify per PR.

[harshad16]

Thank you for the work
/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harshad16

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [harshad16]

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

[harshad16]

/cherrypick stable

[openshift-cherrypick-robot]

@harshad16: new pull request created: #360

In response to this:

/cherrypick stable

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.