wicket: Component order in the update list is different than when paging through the update screen

On the initial Update Status screen that lists all sleds/switches/PSC, the order is sleds 0-31, then switches 0-1, then psc 0. However, on the next screen where updates can be triggered, we allow the operator to move through the same list, but the order is different: sleds 0-15, switch 0, psc 0, switch 1, sleds 16-31. The latter order more closely matches the actual physical order (and matches the rack overview screen); we should make the Update Status list order consistent.

Start by locating the Update Status screen and the paging/trigger-update list described in the issue, then compare how each constructs its component order. Confirm the list matches the physical and rack overview order: sleds 0-15, switch 0, PSC 0, switch 1, sleds 16-31. Run the relevant UI tests if present.