ci(qualification): run Fedora Podman proof-of-concept pipeline

[SDAChess]

Description

Run the first end-to-end release qualification pipeline by composing the Fedora rootless Podman target with the clean-install and N to N+1 forward-upgrade flows and the shared conformance suite.

The workflow must consume the immutable artifacts produced by the release pipeline, retain qualification evidence tied to those artifacts, and report one unambiguous qualification conclusion without duplicating target, flow, or suite implementation.

Context

• Parent release pipeline: feat: 0.1.0 release pipeline #2860
• Reusable release artifacts: chore(ci): clean up release pipeline #1683
• Shared driver conformance suite: spike: driver conformance suite for compute drivers #2183
• Qualification composition contract: feat(ci): compose release qualification from targets, flows, and suites #2972
• Fedora rootless Podman target: ci(qualification): add Fedora rootless Podman target #2973
• Clean-install flow: ci(qualification): add reusable clean-install flow #2974
• Forward-upgrade flow: ci(qualification): add reusable N-to-N+1 forward-upgrade flow #2975

This is the agreed P0 proof of concept before expanding release qualification across the rest of the platform matrix.

Definition of Done

• A manually dispatchable and reusable GitHub Actions workflow accepts an immutable candidate artifact manifest.
• The workflow runs both clean-install and N to N+1 forward-upgrade qualification on the Fedora rootless Podman target.
• Each flow invokes the shared conformance suite from spike: driver conformance suite for compute drivers #2183 rather than embedding separate Fedora or Podman assertions.
• The candidate binaries and packages are downloaded and reused; qualification does not rebuild them.
• Results identify the candidate version, source commit, artifact identities, target, flow, and suite versions.
• Human-readable output, machine-readable results, logs, and target diagnostics are retained for each run.
• An undeclared skip, retry-dependent result, or failed combination produces a failed qualification conclusion.
• The workflow exposes a single pass/fail result that the release pipeline can consume as a publication gate.
• Documentation explains how to run and diagnose the proof of concept locally and in GitHub Actions.