Consolidate duplicate Apple integration-test payloads

## Problem

The Apple integration tests reference both architecture-specific payload paths and older paths without an architecture segment. Several payloads exist in both forms, including iOS simulator, Mac Catalyst, and tvOS simulator test applications.

Keeping parallel copies makes it unclear which payload is authoritative and increases the chance that scouting or manual-command tests continue using an older artifact.

## Proposed work

- Inventory every Apple payload reference used by regular, scouting, and manual-command integration tests.
- Migrate active tests to the architecture-specific `x64` or `arm64` payloads.
- Verify that the architecture-specific payloads cover all current queues and command scenarios.
- Remove repository references to legacy no-architecture paths.
- Delete or archive redundant blobs only after confirming that no supported branch consumes them.

## Completion criteria

- Each active Apple test scenario references one clearly identified architecture-specific payload.
- No current XHarness test references a duplicate no-architecture payload.
- The remaining blob layout and update procedure are documented.

_This issue was created with AI assistance._

Begin by inventorying Apple payload references across the regular, scouting, and manual-command integration tests, including both architecture-specific and no-architecture paths. Verify that x64 and arm64 payloads cover every current queue and command scenario before removing legacy references or redundant blobs. Done means each active XHarness scenario has one identified architecture-specific payload and the remaining blob layout and update procedure are documented.

Written by the indexing model from the issue text.