Add support for custom pod properties to crd

Currently there are no way to pass custom pod configs via crds, like nodeSelector/tolerations/topologySpreadConstraints/affinity/etc (unless I'm missing something?)

There is only arch/zone/region though not sure what exactly they configure, labels?

Start by tracing how the Kubernetes CRDs are defined and how the operator turns them into pod configuration. Compare the existing arch, zone, and region properties with the requested nodeSelector, tolerations, topologySpreadConstraints, and affinity settings. Done means the supported custom properties can be declared in a CRD and are applied to the resulting pod configuration.

Written by the indexing model from the issue text.