Selective test sharding now plans suite shards server-side from history

tuist test --shard no longer needs to boot every test bundle in a simulator just to enumerate suites. Plans that took toward an hour because most modules had to be re-enumerated one-by-one under simulator boot contention are now produced server-side: the CLI ships the module list from the built .xctestrun and the server derives suites and durations from historical TestSuiteRun timings on the build branch, with default-branch fallback. A final catch-all shard runs every suite not assigned elsewhere, so newly added or renamed suites still run. CLIs below the supported canary version still receive the legacy suite shard shape.