3scale Operator lacks support for Jaeger/OpenTracing

Red Hat 3scale API Management mentions that we should use the environment variables OPENTRACING_TRACER and OPENTRACING_CONFIG in order to configure APIcast to use OpenTracing:

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

Ensure the OPENTRACING_TRACER environment variable is set to jaeger. If this is empty, OpenTracing is disabled.
Set the OPENTRACING_CONFIG environment variable to specify the default configuration file of your tracer. See the following example jaeger.example.json file.

However, there doesn't seem to be a way to set up those variables using neither the 3scale-operator nor apicast-operator:

https://github.com/3scale/3scale-operator/blob/master/doc/apimanager-reference.md

https://github.com/3scale/apicast-operator/blob/master/doc/apicast-crd-reference.md

—

There should be a way to configure those Environment Variables on APIcast through the 3scale Operator, otherwise Jaeger/OpenTracing will only be compatible with the template (OCP 3.11) method of deploying 3scale.