[BOP-54] Run CI on a PR

[nwneisen]

What this PR does

Runs CI for vet, unit-tests, and build when a PR is created or updated.

https://mirantis.jira.com/browse/BOP-54

Testing

Tested by merging the PR into my fork of the repo and then opening a PR. Made sure all of the steps ran and passed when changing something other than a MD file.

Notes for Reviewers

These jobs will pretty much be a copy and paste to the other BOP repos. Take a look, checkout the readme, let me know if anything needs to be changed or clarified before copying it to the other repos.

[ranyodh]

Just one small change. Other, looks awesome!

Regarding caching:
It would great if we can figure out dependency caching as well. But, it is not required right now. We can create separate ticket for it.

To be more specific, I referring to the build step which runs make build. The docker build step does not have access to the cache that actions/setup-go@v4 action generates.

[nwneisen]

@ranyodh caching seems like it always seems to be a little tricky. I'll create another ticket to look at doing it by itself and we can get CI running on our PRs with these changes. The docker-build command is also running tests which I don't think we want in local dev or in the CI step. I will take a look at all the Makefile commands closer and we can start to modify them.

[ranyodh]

caching seems like it always seems to be a little tricky. I'll create another ticket to look at doing it by itself and we can get CI running on our PRs with these changes.
Yes, especially inside the docker. Lets do that with another ticket.

The docker-build command is also running tests which I don't think we want in local dev or in the CI step. I will take a look at all the Makefile commands closer and we can start to modify them.

Yes, these make commands comes auto-generated with the operator-sdk. We can modify them as we go.