scripts for prow precommit and crd jobs

[olivercodes]

This is to resolve #37

After chatting with @astoycos we decided it would be better to follow what other sigs have done, and implement a prow job, as well as follow similar patterns for the test scripts (moving to live under hack/).

There will be a second PR for this issue, in test-infra to add the prow job that calls these changes.

p.s. This is my first PR to a kubernetes project, so I'm sure I did something wrong. Please feel free to tell me :).

[netlify]

✅ Deploy Preview for kubernetes-sigs-network-policy-api ready!

Name	Link
🔨 Latest commit	6e6b1a2
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-network-policy-api/deploys/6362876eaefe8d00091363ec
😎 Deploy Preview	https://deploy-preview-47--kubernetes-sigs-network-policy-api.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: olivercodes / name: Bryan Oliver (b534b9b)

[k8s-ci-robot]

Welcome @olivercodes!

It looks like this is your first PR to kubernetes-sigs/network-policy-api 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/network-policy-api has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[astoycos]

Thanks so much for tackling this!!! @olivercodes

This is almost there.

When I run locally I am running into some errors

[astoycos@localhost network-policy-api]$ make verify 
hack/verify-all.sh -v
Skipping hack/../hack/verify-all.sh
Verifying gofmt
Test FAILED: hack/../hack/verify-gofmt.sh 
level=warning msg="[linters context] structcheck is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/2649."
SUCCESS: hack/../hack/verify-golint.sh 
Verifying govet
pattern ./...: lstat /home/astoycos/go/src/github.com/k8s.io/network-policy-api/cache/00/003426ff6eb11828a6df4b2609e8ee569ba24474bc5a96c630c74d47cf5ee675-a: permission denied
no Go files in /home/astoycos/go/src/github.com/k8s.io/network-policy-api
Test FAILED: hack/../hack/verify-govet.sh 
make: *** [Makefile:41: verify] Error 1

[astoycos]

/assign @tssurya

As well if she has some extra time for a look

[tssurya]

woohoo thanks for your contribution @olivercodes!, we were just about to start on the CI parts for the repo and this is great a start, let me try to review this by end of this week. - first thing that came to my mind as I did an overall scroll was if you could squash the cleanup commits that would make history look cleaner..

[astoycos]

@olivercodes This is pretty much there!! Thanks again.

One last nit and also if you could just Sign-off your commit/s while you're at it that'd be awesome!

(I need to work on a contributor guidelines doc or point back to K8s's https://github.com/kubernetes/community/blob/master/contributors/devel/README.md#setting-up-your-dev-environment-coding-and-debugging in our readme)

[olivercodes]

@olivercodes This is pretty much there!! Thanks again.

One last nit and also if you could just Sign-off your commit/s while you're at it that'd be awesome!

(I need to work on a contributor guidelines doc or point back to K8s's https://github.com/kubernetes/community/blob/master/contributors/devel/README.md#setting-up-your-dev-environment-coding-and-debugging in our readme)

Done, and think I got it :)

Fixed that last nit and squased

[astoycos]

Awesome!!! Great first Contribution :)

Let's merge everything and see it all working!

[astoycos]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: astoycos, olivercodes

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [astoycos]

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