Add detailed request logging

[wfchandler]

Currently we don't offer a way to expose the details of the API requests the CLI or other SDK consumers to users, making troubleshooting difficult.

With the new middleware feature available in Progenitor, we can now inject our own logger using the reqwest-tracing crate. This gives us output like:

  $ ./target/debug/oxide --debug disk list --project will | jq .
  {
    "timestamp": "2025-02-26T17:29:23.354297Z",
    "level": "DEBUG",
    "fields": {
      "message": "close",
      "time.busy": "16.7ms",
      "time.idle": "365ms"
    },
    "target": "oxide::tracing",
    "span": {
      "host": "oxide.sys.r3.oxide-preview.com",
      "http.request.method": "GET",
      "http.response.content_length": 998,
      "http.response.status_code": 200,
      "oxide.request_id": "c5e7d65e-bcb2-4ade-a817-6f13b681b19b",
      "url": "https://oxide.sys.r3.oxide-preview.com/v1/disks?project=will",
      "name": "Oxide API Request"
    },
    "spans": []
  }

We will also log the first KiB of the request body, if present. This should be enough to capture the details human-readable requests, e.g. an OxQL query, but avoid too much noise from something like a disk import.

The --debug flag will enable debug logs for both the CLI and any dependencies, such as hyper. To view only CLI logs, set RUST_LOG=oxide=debug.

Closes #1014.

[wfchandler]

Dependent on oxidecomputer/progenitor#1074 oxidecomputer/progenitor#1079

[wfchandler]

Closing in favor of #1053