fix(scripting): derive run device order from the device list instead of storing it

[JamieRuderman]

Follow-up to #1167, addressing the Codex review finding on #1169.

#1167 ordered ui.selected by device-list position at selection time and stored that order. Codex correctly flagged that the order goes stale: changing the sort in FilterDrawer calls devices.set({ sort }) + fetchList(), which reorders the list without any selection click, so sortSelectedIds never re-runs. The run form then displays — and submits — the old order.

List position is mutable, so any stored copy of it can drift. The same applies to filtering, searching, and paging, not just sorting. Deriving the order at the point of display removes the whole class of staleness.

Changes

• ScriptRunPage.resolvedDevices now orders by device-list index. It's already a useMemo over devices, so it recomputes when the list reorders — no extra work, and it covers SELECTED and CUSTOM alike.
• handleRun/handlePrepare submit resolvedDevices.map(d => d.id), so what's displayed is what's sent. CUSTOM runs are now ordered too, where before only SELECTED was touched.
• sortSelectedIds is deleted from helpers/selectionRange.ts and useSelect no longer calls it, so ui.selected goes back to plain click order.

Net effect: 14 insertions, 18 deletions — this removes more than it adds.

Notes

• The useSelect simplification from fix(scripting): sort selected devices by name when added #1167 (collapsed duplicate branches, single dispatch) stays; only the sort call is removed.
• Reverting ui.selected to click order also undoes fix(scripting): sort selected devices by name when added #1167's side effect on the other bulk device actions (tagging, transfer, delete), which never wanted an imposed order.
• Devices not in the current list — a selection outliving a filter change — sort last and keep their relative order.

Testing

tsc --noEmit passes. Not exercised in the running app. The case worth clicking through is the one Codex described: select several devices, change the device list sort, then open the run form and confirm the chips follow the new sort.

[aws-amplify-us-west-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1170.d20k671nqqv4kl.amplifyapp.com