Fix CI: tidy with 1.17

[genevieveluyt]

Description

CI is failing on PRs example

Run make setup
go mod download
go mod tidy
go: downloading k8s.io/klog v1.0.0
go: downloading golang.org/x/crypto v0.1.0
github.com/Shopify/kubeaudit/internal/k8sinternal imports
	k8s.io/client-go/plugin/pkg/client/auth/azure imports
	github.com/Azure/go-autorest/autorest/adal imports
	golang.org/x/crypto/pkcs12 loaded from golang.org/x/crypto@v0.0.0-20220214200702-8[6](https://github.com/Shopify/kubeaudit/actions/runs/3965679250/jobs/6795640603#step:6:7)341886e292,
	but go 1.16 would select v0.1.0
github.com/Shopify/kubeaudit/internal/k8sinternal imports
	k8s.io/client-go/plugin/pkg/client/auth/azure imports
	github.com/Azure/go-autorest/autorest/adal imports
	golang.org/x/crypto/pkcs12 imports
	golang.org/x/crypto/pkcs12/internal/rc2 loaded from golang.org/x/crypto@v0.0.0-20220214200[7](https://github.com/Shopify/kubeaudit/actions/runs/3965679250/jobs/6795640603#step:6:8)02-[8](https://github.com/Shopify/kubeaudit/actions/runs/3965679250/jobs/6795640603#step:6:9)6341886e2[9](https://github.com/Shopify/kubeaudit/actions/runs/3965679250/jobs/6795640603#step:6:10)2,
	but go 1.16 would select v0.1.0

To upgrade to the versions selected by go 1.[16](https://github.com/Shopify/kubeaudit/actions/runs/3965679250/jobs/6795640603#step:6:17):
	go mod tidy -go=1.16 && go mod tidy -go=1.[17](https://github.com/Shopify/kubeaudit/actions/runs/3965679250/jobs/6795640603#step:6:18)
If reproducibility with go 1.16 is not needed:
	go mod tidy -compat=1.17
For other options, see:
	https://golang.org/doc/modules/pruning
make: *** [Makefile:50: setup] Error 1
Error: Process completed with exit code 2.

Type of change

• Bug fix 🐛
• New feature ✨
• This change requires a documentation update 📖
• Breaking changes ⚠️ (removes backwards compatibility with go 1.16)

How Has This Been Tested?

• Test A
• Test B

Checklist:

• I have 🎩 my changes (A 🎩 specifically includes pulling down changes, setting them up, and manually testing the changed features and potential side effects to make sure nothing is broken)
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The test coverage did not decrease
• I have signed the appropriate Contributor License Agreement

[dani-santos-code]

thanks for fixing it! 🙏