feat(tracing-apps): update jaeger-operator from 2.29.* to 2.32.2

[Nerkho]

Description

Update jaeger-operator from 2.29.* to 2.32.2 (operator version 1.31 to 1.34.1)

Issues

• Fixes Version 2.32.2 of jaegerOperator is available! #720

Changes

• [jaeger-operator] update to 1.34.1 jaegertracing/helm-charts#367 CHANGELOG.md
  • 1.34.1
    • Fix: storage.es.tls.enabled flag not passed to es-index-cleaner (#1896)
    • Fix: jaeger operator fails to parse Jaeger instance version (#1885)
    • Support Kubernetes 1.24 (#1882)
    • Cronjob migration (#1856)
    • Fix: setting default Istio annotation in Pod instead of Deployment (#1860)
    • Add http- prefix to port names in collector and agent services (#1862)
  • 1.33.0
    • Adding priority-class for esIndexCleaner (#1732)
    • Fix: webhook deadlock (#1850)
    • Fix: take namespace modifications into account (#1839)
    • Replace deployment reconciler with webhook (#1828)
    • Add managed by metric (#1831)
    • Fix admissionReviews version for operator-sdk upgrade (#1827)
    • Make RHOL Elasticsearch cert-management feature optional (#1824)
    • Update the operator-sdk to v1.17.0 (#1825)
    • Fix metrics selectors (#1742)
  • 1.32.0
    • Custom Image Pull Policy (#1798)
    • add METRICS_STORAGE_TYPE for metrics query (#1755)
    • Make operator more resiliant to etcd defrag activity (#1795)
    • Automatically set num shards and replicas from referenced OCP ES (#1737)
    • support image pull secrets (#1740)
    • Fix webhook secret cert name (#1772)
• [jaeger-operator] Add cert machinery jaegertracing/helm-charts#368
  • Fixes jagger-operator 1.32.0 fails to start successfully jaegertracing/helm-charts#351
• [jaeger-operator] Add compatibility matrix jaegertracing/helm-charts#371
• [jaeger-operator] Refactor CRD to allow Jaeger CR creation on initial install jaegertracing/helm-charts#372

Checklist

• This PR contains a description of the changes I'm making
• I updated the version in Chart.yaml
• I updated applicable README.md files using pre-commit run
• I documented any high-level concepts I'm introducing in docs/
• CI is currently green and this is ready for review
• I am ready to test changes after they are applied and released