Support Tempo deployments in monolithic mode

[andreasgerstmayr]

The operator should support Tempo deployments in monolithic mode.
For example local filesystem and in-memory storage is only available in monolithic deployments.

Design doc: https://docs.google.com/document/d/1fbBfXddfukj6Pfkr8rtRfUj522pIk5JKBzA_WyppPW0

Tasks

Beta Give feedback

1. In-memory storage: Support monolithic deployment mode #722
2. PV storage: Support monolithic deployment mode #722
3. Object storage: Support object storage in TempoMonolithic CR #763
4. Ingestion OTLP/gRPC: Support monolithic deployment mode #722
5. Ingestion OTLP/HTTP: Support monolithic deployment mode #722
6. Ingestion TLS: Support configuring mTLS for ingestion in TempoMonolithic CR #756
7. Jaeger UI: Support monolithic deployment mode #722
8. Jaeger UI Ingress+Route: Support creating Ingress and Route objects in the TempoMonolithic CR #755
9. Multitenancy/Gateway: Support multi-tenancy in TempoMonolithic CR #816
10. Observability: ServiceMonitor, PrometheusRules, GrafanaDatasource: Support observability in TempoMonolithic CR #793
11. Overlay config: Support monolithic deployment mode #722
12. Management State: Support monolithic deployment mode #722
13. Resources/Limits: Support configuring resource requests and limits in TempoMonolithic CR #771
14. Operand status field: Add status field to TempoMonolithic CR #787
15. Upgrade: Support upgrading TempoMonolithic CR #850
16. Tolerations (Support nodeSelector, tolerations and affinity in TempoMonolithic CR #782)
17. support custom service account: Support custom ServiceAccount in TempoMonolithic CR #836
18. TLS Profile: Support TLS Profile with TempoMonolithic CR #862
19. watch external resources (storage secret, T config map and secret)

[pavolloffay]

Closing as done