Trace namespace SHOULD be a template parameter

[esnible]

It isn't possible to configure the trace namespace without regenerating the templates.

This means that oc process can't alter the namespaces. They aren't configurable.

resources/services/observatorium-traces-template.yaml has { name: 'OBSERVATORIUM_TRACES_NAMESPACE', value: 'observatorium-traces' }, in the Jsonnet.

It gets substituted in the correct places by resources/services/observatorium-template.yaml

- --experimental.traces.read.endpoint-template=http://observatorium-jaeger-{tenant}-query.${OBSERVATORIUM_TRACES_NAMESPACE}.svc.cluster.local:16686/
...
--experimental.traces.read.endpoint-template=http://observatorium-jaeger-{tenant}-query.${OBSERVATORIUM_TRACES_NAMESPACE}.svc.cluster.local:16686/

The problem is that the substitution happens when the Templates are being made. Rather than being something that is fixed during template generation, the traces namespace SHOULD become an OpenShift template parameter similar to NAMESPACE, OPENTELEMETRY_OPERATOR_NAMESPACE or JAEGER_OPERATOR_NAMESPACE.

cc @pavolloffay