fix: Set spec.hard.pod value to string

[OpenSourceZombie]

What this PR does / why we need it:
Fixes v3.7.1 on k8s 1.20 with server side apply

Special notes for your reviewer:
When deploying v3.7.1 using deploy/gatekeeper.yaml with server side apply I get

# Error from server: failed to create typed patch object: .spec.hard.pods: expected string, got &value.valueUnstructured{Value:100}

From the examples here https://kubernetes.io/docs/concepts/policy/resource-quotas/#resource-quota-per-priorityclass this value should be a string not an integer

[sozercan]

@OpenSourceZombie thanks for the PR!

This is auto-generated. Can you revert your current change and make changes in:

gatekeeper/config/manager/manager.yaml

Line 198 in 1f8b3ea

pods: 100

gatekeeper/cmd/build/helmify/static/values.yaml

Line 54 in b524d53

podCountLimit: 100

then run make manifests.

Looks like DCO needs to be signed and needs a semantic pr title too.

[sozercan]

see comment

[maxsmythe]

Also, this will get clobbered by the config autogen process unless it also gets updated here:

gatekeeper/config/manager/manager.yaml

Lines 191 to 204 in cdd14e0

	apiVersion: v1
	kind: ResourceQuota
	metadata:
	name: critical-pods
	namespace: system
	spec:
	hard:
	pods: 100
	scopeSelector:
	matchExpressions:
	- operator: In
	scopeName: PriorityClass
	values:
	- system-cluster-critical

[OpenSourceZombie]

@sozercan - updated and signed my commits.

[sozercan]

Sorry for the delay, LGTM