Combining same-name components as variants gives each one the first
unused "Value N", in the order the mains enter the variant container.
`generate-combine-as-variants` moved all the remaining mains in one
relocation, which takes them in layer order, so the values followed the
layers and not the combine order. It now moves them one at a time, in
the order of the ids, as the frontend combine on develop does.
Test: `test-combine-as-variants-same-name-values-follow-combine-order`.
Benchmark (scripts/bench-components, ms, lower 2.5% quantile):
| :world | :baseline | :now | :mean | :ratio |
|------------------------------------+-----------+--------+--------+--------|
| deepest-edit-through-three-levels | 35.215 | 20.749 | 21.213 | 0.59 |
| edit-through-a-chain-of-dependents | 68.931 | 40.771 | 41.457 | 0.59 |
| library-update-into-copies | 83.083 | 50.674 | 51.835 | 0.61 |
| main-edit-among-many-shapes | 4.837 | 1.967 | 2.133 | 0.41 |
| main-edit-into-10-copies | 1.79 | 1.039 | 1.059 | 0.58 |
| main-edit-into-100-copies | 15.415 | 9.153 | 9.626 | 0.59 |
| main-edit-into-1000-copies | 153.086 | 93.347 | 99.626 | 0.61 |
| variant-switch-into-copies | 32.052 | 21.86 | 22.36 | 0.68 |
AI-assisted-by: claude-opus-5-5