Allow image and tag to be specified separately for target allocators

[rorynickolls-skyral]

Component(s)

collector, target allocator

Describe the issue you're reporting

Currently, the image for a target allocator can be specified with the targetAllocator.image field on the OpenTelemetryCollector custom resource.

This means that it is not possible to supply an image registry and tag separately.

An example of when this would be useful is when pulling images from a private mirror but wanting to keep the tag up-to-date automatically.

Currently, to pull images from a private registry a user must also pin the target allocator tag in their custom resource. It would be preferable to only set the registry and have the operator select the target allocator tag itself.

[swiatekm]

Both the target allocator and collector image can be set using the same mechanism as built-in K8s resources like Deployments or StatefulSets. If you want to track updates to the image tag separately, it's preferable to do that using a higher level templating tool, like Helm or kustomize. The operator Helm Chart, for example, already lets you do this.