Add latency test to diagnostics report

Users have reported unexpected slowness while using a live QPU that seemed to be due in part to strangely high latency in gRPC requests during program translation, submission for execution, and results retrieval.

A latency detection utility in the diagnostics report could help diagnose these issues.

Currently the diagnostics report looks like the following:

pyQuil version: 4.14.3
qcs-sdk-python version: 0.21.18
Python version: 3.11.12 | packaged by conda-forge | (main, Apr 10 2025, 22:23:25) [GCC 13.3.0]
Python implementation: cpython
Python implementation version: 3.11.12
Python C API version: 1013
Python executable: /opt/conda/envs/python3/bin/python
venv prefix: /opt/conda/envs/python3
platform: linux
qcs-sdk-rust version: 0.25.13
rustc version: rustc 1.85.1 (4eb161250 2025-03-15)
features: EXPERIMENTAL, TRACING, TRACING_CONFIG, TRACING_OPENTELEMETRY
qcs:
  address: https://api.qcs.rigetti.com/
  network reachable: true
quilc:
  address: tcp://127.0.0.1:5555
  version: 1.26.0
  available: true
qvm:
  address: http://127.0.0.1:5000/
  version: 1.17.2 [266c11e]
  available: true
libquil:
  available: false
  quilc version: -
  qvm version: -

Start by locating the diagnostics report implementation linked from the issue and trace how it gathers QCS, translation, execution-submission, and results-retrieval information. Define what latency data the report should expose for each gRPC phase, then verify the report includes those measurements alongside its existing output.