Consolidate duplicate Apple integration-test payloads

[vitek-karas]

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.

[matouskozak]

I believe

Migrate active tests to the architecture-specific x64 or arm64 payloads.

should be already done, so if we remove servicing branches #1668 we should be fine with removing the older binaries.