Add troubleshooting notes

[albertteoh]

Which problem is this PR solving?

Document the troubleshooting steps taken while investigating this support question.

One of the problems faced by users was caused by OpenTelemetry Collector Contrib v0.85.0 introducing a breaking change to enable normalized metric names by default:

prometheusexporters: Append prometheus type and unit suffixes by default in prometheus exporters. (https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/26488) Suffixes can be disabled by setting add_metric_suffixes to false on the exporter.

Relates to: https://github.com/jaegertracing/jaeger/pull/4957

Description of the changes

• Adds the following troubleshooting guides:
  • Inspecting the Prometheus queries that Jaeger makes to fetch data for the Monitor tab.
  • Inspecting OpenTelemetry config to troubleshoot a possible cause for missing error metrics.
• Updates only made from when SPM defaulted to supporting the spanmetrics connector, which was v1.49.0.

Checklist

• [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• [x] I have signed all commits ~- [ ] I have added unit tests for the new functionality~ ~- [ ] I have run lint and test steps successfully~

[netlify[bot]]

✅ Deploy Preview for romantic-neumann-1959d7 ready!

Name	Link
🔨 Latest commit	212a218bbd734ef3a6f0443d054cb6d33e52436d
🔍 Latest deploy log	https://app.netlify.com/sites/romantic-neumann-1959d7/deploys/655840ae99e9d000083ef4d5
😎 Deploy Preview	https://deploy-preview-660--romantic-neumann-1959d7.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.