Feature Request: PolicyServer CRD should expose anti-affinity rules

[flavio]

Is your feature request related to a problem?

This is part of this epic.

Solution you'd like

Extend the PolicyServer CRD by adding a new attribute called affinity of type v1/Affinity.

This object, when set, is then copied into the PodSpec of the Policy Server Deployment by our controller.

The default helm chart should then allow this affinity value to be set for the default Policy Server it creates.

Acceptance criteria

• The PolicyServer CRD has an attribute affinity of type v1/Affinity
• The value of PolicyServer.spec.affinity is propagated into the Deployment spec of PolicyServer
• [affinity/anti-affinity] The helm charts are updated to allow tuning of these new attributes #701
• [affinity/anti-affinity] The CRD documentation is updated to reflect this change #702
• [affinity/anti-affinity] The project documentation mentions this new attribute #703
• Expose anti-affinity, PDB, limits and requests in questions.yaml helm-charts#418

[viccuad]

Skipping exposing this new features through Rancher UI, see kubewarden/helm-charts#418.

With that, this is done, will get shipped on the next release.