Suite-level test sharding now distributes shards using correct per-suite timing

Splits based on individual test suites were collapsing into a single shard even when the configured per-shard duration target should have produced many shards. The server now keys historical suite timing by the full module-qualified name (Module/Suite) that the CLI sends, matching the lookup used by the shard planner. This gives each suite its real duration estimate, so the bin packer can distribute suites across the correct number of shards. If you want very small per-shard targets on a large suite set, raise –shard-max above the default 10; otherwise the planner stays capped at that limit.