Fixed suite-granularity selective test sharding collapsing to a single shard

Fixed suite-granularity shard plans collapsing to a single shard. The historical timing lookup used the bare suite name on the server side, while the CLI sends suites as Module/Suite, so lookups always missed and fell back to the median duration. This made the bin packer estimate the total time far too low and compute only 1 shard, no matter how large the suite set was. The server now joins test suite runs to test module runs and keys the timing map on the module-qualified name. Suite-granularity shard plans now fan out correctly across multiple shards, and same-named suites in different modules are no longer conflated.