[appmesh-jaeger/appmesh-controller] Allow ability to specify Jaeger init container image source

**Is your feature request related to a problem?**
The appmesh-jaeger/appmesh-controller helm charts don't provide any configuration options for the "inject-jaeger-config" init container and pulls a busybox image from Dockerhub by default. This causes issues for users whose security configuration doesn't allow for direct access to Dockerhub.

**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
appmesh-jaeger and/or appmesh-controller

**Describe the solution you'd like**
A configuration option in appmesh-controller and/or appmesh-jaeger that allows for the specification of the "inject-jaeger-config" image source similar to how appmesh-controller allows for the specification of the envoy image source.

**Describe alternatives you've considered**
X-ray isn't compatible with Fargate for EKS due to limitations on the usage of Daemonsets, Datadog requires additional licensing agreements and payment.

Start with the appmesh-controller and appmesh-jaeger Helm chart values and templates, and compare them with the existing Envoy image source configuration. The work is done when the inject-jaeger-config init container image source can be configured and the rendered chart uses that value instead of Dockerhub by default.

Written by the indexing model from the issue text.