pullPolicy for brokerJob fetched from wrong section of values.yaml

[melinda-mytra]

Describe the bug
In values.yaml, the image pullPolicy is listed under .Values.[type].configuration.brokerPod.image.pullPolicy.
However the pullPolicy actually used comes from a level up at .Values.udev.configuration.pullPolicy.

That means specifying the pullPolicy as documented in values.yaml has no effect.

Expected behavior
The pullPolicy documented in values.yaml is also the one used in the templates.

I'd imagine the templates should change, since the pullPolicy in the values is in the expected place, but either way around would work.

[kate-goldenring]

@melinda-mytra nice find. I agree that fixing this in the templates so jobs use the same pattern as pods is the right approach. Would you be willing to take this on?