WARN about non-empty additionalProperties in CRs

If users make a trivial mistake in their custom resource (for example a typo) the apiserver will accept the resource, and the operator (any of them) currently puts such properties in the additionalProperties property of the api object. From outward appearances the operator will use the defaults for the misspelt property. To the user this looks like a bug.

We should visit each of the nodes in the CR and have warn logging about each of the properties found there. We need to do this for all operators.