Suite-level test sharding now fans out correctly instead of collapsing to one shard

Suite-granularity test sharding in Tuist Cloud now matches historical suite timings against the same module-qualified names the Tuist CLI sends (for example, Module/Suite), so shard plans no longer collapse to a single shard. Previously the server keyed timing data on the bare suite name, so every lookup fell back to the median duration, making the bin packer underestimate total runtime by roughly 100x and return 1 shard. This fix also prevents same-named suites in different modules from being conflated. If your per-suite target duration is tight, remember that –shard-max still caps the number of shards.