Report worker UXarray version uniformly across all remote compute ops

[rajeeja]

Summary

Extends the remote-provenance transparency introduced in #71 so that every
compute and analysis remote function reports the HPC worker's true UXarray
version, uniformly.

Background

#71 added remote_uxarray_version + a version-drift warning, but only for a
subset of remote functions. Some compute paths (inspect_variable,
azimuthal_mean, grid_facts) still omitted the worker version, so their
results could not surface local/remote version drift.

What changed

• Added _worker_uxarray_version to the remaining compute/analysis remote
  functions: remote_inspect_variable, remote_calculate_azimuthal_mean,
  remote_grid_facts (the others already had it).
• All 13 compute/analysis remote functions now report the worker version;
  _run_on_hpc surfaces it as remote_uxarray_version in provenance and emits
  a drift warning when it differs from the local version. The internal key
  is stripped from the user-facing result.
• Plot functions are intentionally out of scope (they return image payloads, not
  numerical results where version drift matters).
• Docs: provenance.md notes the coverage is now uniform across compute ops.

Testing

• uv run pre-commit run — all hooks pass.
• uv run pytest tests/ --ignore=tests/test_remote_agent.py — 338 passed
  (2 new: a regression test asserting every compute remote function reports the
  version, and a _run_on_hpc drift-warning unit test).
• Live on Chrysalis: inspect_variable and get_capabilities now report
  remote_uxarray_version and emit the drift warning (the worker runs an older
  uxarray than local); the internal _worker_uxarray_version key does not leak
  into results.