web | api | docs: Search, sort and manual ordering for projects and services - #28

Closes UNB-397. Adds search, sort and manual ordering to the projects page and the services page.

Search and sort

• Search: filters by name. On lg and up it sits next to the New Project / Add button. Below that it takes a full row above the cards, lined up with the grid. On the services page, searching a group's name shows the whole group. Ctrl+K works as before.
• Sort: an icon button next to the search, built like the metrics filter button, with a Reset Sort item. The options are Custom (default), Newest First, Oldest First, A → Z and Z → A.
• URL state: search and sort live in the URL (search, sort). Defaults are left out, and an invalid sort falls back to Custom.
• No results: an empty state with a Clear Search button.

Manual ordering

• Dragging: on Custom with no search, team editors (projects) and environment editors (services) can drag cards into place. A short click or tap still opens the card: a drag starts after 6px with a mouse, or a 250ms press on touch. With a keyboard, Space picks a card up, the arrow keys move it, and Space or Enter drops it.
• Service groups: a group moves as one block, and its services are ordered inside it. A service can't be dragged out of its group. While dragging services, the list itself is reordered and a copy follows the pointer, because groups and service cards differ in size.
• Sharing: the order is stored in the API and shared by everyone in the team or environment.

API and MCP

• Storage: position on projects, services and service groups. Groups and ungrouped services share the environment's order, and grouped services have their own order inside the group.
• Placement:
  • new projects, services and groups go to the top;
  • a service joining a group goes to the top of that group, and one leaving goes to the top of the environment;
  • deleting a group keeps its services where the group was.
• Default order: with every position at 0 (all existing data), ties fall back to newest first, which is the order the UI shows today.
• New endpoints: reorder-projects, reorder-services and reorder-service-group, each also an MCP tool. Items left out keep their order after the listed ones. Duplicates and items from elsewhere answer 400. Reordering leaves updated_at alone.
• List sorting: list-projects and list-service take sort_by (custom, name, created_at, updated_at) and sort_order. They default to newest first, and the UI asks for custom.
• Migrations: project_position and service_position.

Shared code

• SearchInput (also used by the service settings search)
• SearchSortToolbar
• useSearchSortParams
• list-sort
• card-sorting (drag helpers)
• one reorder helper in the API repositories

Docs: ordering sections on the projects and service groups pages, and the new MCP tools.