Bump tempo to 2.2.0

[mibr020]

Summary

Staggering upgrades to deal with the least amount of potential breaking changes.

Ultimate goal is to get to 2.6.0

Test Plan

1. Made the necessary updates to Chart and Values, after checking dependencies here https://artifacthub.io/packages/helm/grafana/tempo-distributed/1.5.0
2. Ran helm dependency update tempo/helm/tempo/
3. Used plural link ... to link to my local project
4. Ran plural build --only tempo --force && plural deploy
5. Monitored for a day, no crashes, restarts, or real disruption of service

Checklist

• No images hosted from dockerhub
• Are dashboards present to understand the health of the application. There must be at least 1 of these
  • all databases should have dashboards
  • ideally also have at least cpu/mem utilization dashboards for webserver tier of the app
  • you can use plural from-grafana to convert a grafana dashboard found via google to our CRD
• Are scaling runbooks present
  • all databases must have scaling runbooks
  • you can use the charts in pluralsh/module-library to accelerate this
• do you need to add config overlays?
  • inputing secrets
  • configuring autoscaling
• If there’s a web-facing component to the app, we need to support OIDC authentication and setting up private networks if no authentication option is viable
• All major clouds must be supported
  • Azure
  • AWS
  • GCP