Fixed suite-level sharding so large test suites split into the expected number of shards

Suite-granularity shard plans previously collapsed to a single shard because the server looked up historical test timings by bare suite name while the CLI sent module-qualified names. The timing lookup now uses the module-qualified name, so duration estimates are accurate and the bin packer creates the right number of shards for your per-shard target.