Normalized error for the SDK facade.

The generated openapi-generator client returns three different shapes for failures (spec-declared error models as {:ok, error_struct}, undeclared statuses as {:error, %Tesla.Env{}}, and transport failures as {:error, reason}). normalize/1 collapses all of them into {:error, %ExDaytona.Error{}} so facade callers match one shape:

• status — HTTP status, or nil for transport failures
• message — human-readable message
• code — the API's error code string, when it sent one
• details — the raw error payload (decoded map, model struct, or transport reason) for anything the other fields don't capture

Response metadata (populated when the failing call carried it — facade calls and generated calls made with response: :full):

• headers — normalized response headers
• request_id — provider request/correlation id
• rate_limit — %{limit, remaining, reset} when the provider sent it
• retry_after — parsed Retry-After seconds
• retry_count — transport retries the SDK performed

Outcome classification

outcome distinguishes what the failure proves:

• :definite — the provider answered; the request was rejected or completed with a known response
• :unknown — the transport failed (timeout, connection loss) and a non-idempotent request MAY have been accepted before the failure. For idempotent requests an :unknown outcome is safe to retry; for POSTs the application must reconcile before retrying.