Jaeger: Deploy operator to staging via Tanka

This issue is part of &210 (closed).

Depends on:

• https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11373 Jaeger: Determine initial configuration for jaeger-operator
• https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11446 Jaeger: Install jaeger-agent via chef
• https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11370 Productionize tanka workflow for observability

Once we know what our jaeger-operator config should look like, we can actually get it deployed to staging.

We've decided to give tanka a shot in ~"team::Observability". So it makes sense to use it for this work, as an alternative to helm.

• namespace in k8s create manually
• ip and dns: https://ops.gitlab.net/gitlab-com/gitlab-com-infrastructure/-/merge_requests/2140
• user in ES
• secrets creation from tanka-deployment/environments/jaeger/README.md
• tanka deployment: gitlab-com/gl-infra/k8s-workloads/tanka-deployments!28 (merged)
• manual IAP config