chore(examples): fix Test Examples CI failures (#5199)

* chore(examples): migrate dotnet SDK image from pyroscope/ to grafana/ org

pyroscope/pyroscope-dotnet:0.15.0-glibc does not exist on Docker Hub.
The image was moved to the grafana/ org. Update all Dockerfiles to use
grafana/pyroscope-dotnet:0.15.0-glibc.

* chore(examples): pin grafana/tempo to 2.10.5

grafana/tempo:latest is now Tempo 3.x which removed the top-level
`ingester` and `compactor` config fields used in our tempo.yml files,
causing container startup failures. Pin all tracing examples to
2.10.5, the latest 2.x release where these fields are still valid.

* chore(tools): fix update_examples for dotnet org change and add tempo updater

- Fix updateDotnet() regex/replacement to use grafana/pyroscope-dotnet
  instead of pyroscope/pyroscope-dotnet
- Add --tempo flag and updateTempo() function that fetches tags from
  grafana/tempo and updates all tracing docker-compose files to the
  latest 2.x release
- Add java-wall and tools/tracing to the list of files updated by tempo

* fix(examples): fix dotnet NuGet package version conflict

OpenTelemetry.Exporter.OpenTelemetryProtocol 1.15.3 transitively
requires System.Diagnostics.DiagnosticSource >= 10.0.0, but the
project pinned 8.0.1 causing NU1605 error on dotnet publish.

Align all OpenTelemetry packages to 1.15.3 and remove the explicit
DiagnosticSource pin to let NuGet resolve the correct version.

* fix(examples): fix dotnet and python/fastapi build failures

dotnet: downgrade OpenTelemetry packages from 1.15.3 to 1.15.2 —
OpenTelemetry.Instrumentation.AspNetCore 1.15.3 does not exist on
NuGet (latest is 1.15.2).

python/fastapi: bump base image from python:3.9 to python:3.11 —
pyroscope-io==1.0.4 requires cffi>=2.0.0 which dropped Python 3.9
support.