support jaeger integration with production strategy

Currently our Jaeger integration only support all-in-one-in-memory mode [1] which means no jaeger persistence. Jaeger support persistence like production strategy using elasticsearch [2] but it looks like we don't support it as of now. see case https://access.redhat.com/support/cases/#/case/03170739 

The key block is the `jaeger_config.json` cannot specify `jaeger-agent:6831` in "localAgentHostPort" since the production strategy of jaeger does not deploy a jaeger-agent:6831 svc.

[1]https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.11/html/administering_the_api_gateway/introduction-to-advanced-operation-of-threescale-apicast-api-gateway_api-gateway-apicast#installing_jaeger_on_your_openshift_instance 

[2] https://docs.openshift.com/container-platform/4.6/distr_tracing/distr_tracing_install/distr-tracing-deploying-jaeger.html