Test sharding plans are built from server-side history

The CLI no longer boots every test bundle to enumerate suites while creating a shard plan. It sends the test modules from the built .xctestrun to the server, which derives suite inventory from historical branch data and balances shards by historical runtimes. A final catch-all shard runs newly added or unknown suites. This removes the simulator boot contention that could silently drop test targets.