feat: register pending setup baseline campaign

[Jammy2211]

Adds the pending setup-baseline campaign and collection/acceptance task to Pulse, linked to the project's draft specification. The board keeps both at needs-decision: implementation of readiness tooling does not authorize measurements or accept baselines.

Project specification: PyAutoLabs/autolens_profiling#385 (merge project first).

Scripts Changed

No executable source changed. Added campaigns.yaml metadata and tasks/setup_baseline_campaign.md; regenerated the board offline.

The task names unresolved revisions, datasets/settings, hardware/threads/load, method/correctness decisions, CPU ral routing and the unavailable compile builder. Collection and scientific acceptance require later separate human decisions. Existing campaigns, last_checkin, snapshots and receipts are preserved.

Validation

189 tests passed; Ruff/format and offline board validation passed. Independent Sol high-effort review CLEAN over tree 30039505bfb3d96b71fc168b0a52ab3c71070f4d, including 11 campaign tests and preservation/render checks. Project links are pinned to reviewed project commit 62a6ad1e82735e360c7cf25be62253a286493b17; the final link-only substitution and offline render were rechecked.

Closes #17. Readiness implementation only; the domain collection task stays pending after merge. Human /prm; no jobs, pin changes, archive acceptance or temporal charts.

Ship gate

Current Heart YELLOW explicitly acknowledged by the human for these two Phase 6 PRs:

• autogalaxy_workspace: open PR 7d old
• autolens_workspace: open PR 7d old
• euclid_strong_lens_modeling_pipeline: open PR 7d old
• release validation stale: source moved since rehearsal (PyAutoNerves)
  No RED override, merge authority, release or profiling-job authorization.