refactor(order)!: retire deprecated order flow

[jorgeparavicini]

WIP / draft — step 1 of the deprecated-endpoint removal is done; steps 2–3 are gated on a backend field (see below). Do not mark ready yet.

Goal

Remove all SDK references to the deprecated GET /pipeline/{pipelineId} and GET /workflow/{workflowId}/progress endpoints, then drop the generator keep-list so they fall out of the generated client on a clean regen. The backend keeps serving them (other consumers exist), but the SDK stops using them. Follows #829 (job-progress migration).

Step 1 — order-flow retirement (this commit) ✅

RapidataOrder is deprecated (order creation is superseded by Jobs). Removed its use of the deprecated endpoints:

• display_progress_bar() — used the workflow-progress endpoint. Removed.
• preview() — resolved the campaign id by unpacking the pipeline. Removed.
• get_results(preliminary_results=...) — the preliminary path used the pipeline preliminary-download endpoints. Removed the arg; get_results() still returns final results via download-results (unchanged, non-deprecated).
• the order-creation campaign-preview QR (unpacked the pipeline). Removed.
• now-dead pipeline/workflow-unpacking helpers + _retry_operation.

BREAKING: display_progress_bar(), preview(), and the preliminary_results arg of get_results() are gone from RapidataOrder.

Step 2 — definition-creation QR (GATED, pending) ⏳

The campaign-preview QR after job-definition creation still resolves the campaign id via GET /pipeline/{pipelineId} (no jobId exists at that point). Waiting on the backend to re-add the definition's preview campaign id to CreateJobDefinitionEndpoint_Output + GET /job/definition/{definitionId}; then the SDK reads it directly and drops the pipeline lookup.

Step 3 — drop keep-list + clean regen (GATED, pending) ⏳

After step 2, remove the keep-list in openapi/generate-schema.sh and regenerate cleanly so the deprecated endpoints (and the rest of the deprecated workflow-results tree) fall out. Before that regen: audit that no high-level wrapper references any endpoint the regen will strip; if one does, stop and escalate rather than re-adding a keep-list.

Verification (step 1)

• uv run pyright src/rapidata/rapidata_client → 0 errors
• uv run pytest → 136 passed, 4 failed — the 4 are pre-existing on main (audience cost-warning / explicit-content tests), unrelated.
• get_results() (download-results) unaffected.
• No docs referenced the removed order features.

🔗 Session: https://poseidon.rapidata.internal/chat/node-f6b42c70