Choose the order of services

[karl-cta]

What and why

Services are listed by name everywhere. With more than a handful, people want the important ones first, in the order their team thinks about them. This lets an editor choose that order from the Services page.

• New position column on services. Existing services start in the alphabetical order they were shown in; a new service goes last. Services sharing a position (a seed that leaves it out) fall back to their name.
• The order applies wherever services are listed: Services page, dashboard and public page, event form, event filters, and the service labels of an event.
• Moving a service does not change its last update time: the update trigger skips position changes, and the migration replaces it before numbering.
• POST /services/order saves the whole order at once, for publishers. A list that is not exactly the current services is refused, and the page reloads: another tab or member changed the list meanwhile.
• Services page: a Change order button opens a mode where each row keeps its name and gains an up and a down arrow in place of its state, pencil and history. A row moves at once, the focus stays on its arrows, a screen reader hears the new position, and the order is saved shortly after the last press, or on Done, Escape or leaving the page. The button keeps the width of its longer label, so the header does not shift.
• The first launch now creates services in the order they were picked.
• New browser test: create a service, find it last, move it up, reload.

Checklist

• cargo fmt --check, cargo clippy --all-targets -- -D warnings and cargo test pass
• I agree to the Contributor License Agreement