`Deny` mode is a bad API with a useful goal: to ensure that policies
MUST match the rule, essentialy adding AND semantics on top of the ALLOW
policies OR semantics.
Deny is trick, because you often end up having double negatives.
For example `deny: !(port in [443, 8443])`. Or worse, somethign like
`deny: jwt.group != 'eng'`; if the jwt doesn't have a `group` this rule
will not deny.
Instead, this proposes adding a new Require mode which is like deny but
inverted.
The above rules would be `require: port in [443, 8443]` or `require:
jwt.group == 'eng'`.
These are useful for admin level rules that apply on top of user level
rules like `require: source.address not in [banned country cidr ranges]`
etc
Reverts agentgateway/agentgateway#1065 because the unittests didn't use
a real k8s API server. A real k8s rejects any CRD that attempts to use a
null map value, and you cannot easily change the CRD because
controller-tools is opinionated about that. I don't want to add new
'remove' APIs for this edge case or kustomize a CRD.
Fixes a TODO:
```
metadata:
labels:
# You'd think this would remove the app.kubernetes.io/instance label,
# but it just sets the label to the empty string. TODO(chandler):
# Figure out the incantation to cause removal of the label.
app.kubernetes.io/instance: null
```
---------
Signed-off-by: David L. Chandler <david.chandler@solo.io>