Revisit Metrics and Tracing integrations

[TimHess]

Follow ups from #1278:

• Is there significant value in the Steeltoe Tracing package? Compare with what Aspire does with regard to OpenTelemetry, maybe Steeltoe should exit this space or provide a slimmer way of helping users set up tracing
• Export to Jaeger has been deprecated in favor of OTLP, we should remove Jaeger references
• Wavefront integration does not behave like the other exporters (eg: private reference), it should align better
  • The Wavefront exporter should be tested against Wavefront again. I noticed the tracing sample will fail repeatedly sending metrics with the non-key that's configured, should we do more than check for the presence of a Uri when turning that on?

Work on adding Zipkin support for OTLP has begun here, but does not yet look ready for the Zipkin exporting to go away

Additionally, with regard to metrics, specifically Prometheus:

• Does the actuator actually behave like an actuator? It looks like we're just configuring OpenTelemetry, I'm not sure it's actually integrated
• Does everything with the exporter actually work? While updating management samples, Prometheus scraping did not work. Encountered error: invalid metric type "CLR memory usage gauge"

[TimHess]

I don't think we need to review what Aspire does in this space anymore, and the Wavefront functionality should be removed.

With current versions of relevant libraries, distributed tracing easily works between .NET and Spring apps.

Please let us know if you aren't happy with any of the above.