trail list: push filters, limit, and pagination to the server

The list endpoint paginates (default 50 rows, max 200), but the CLI fetched it bare and filtered client-side, so only trails among the 50 most recently updated were ever visible and the shown/total counts were computed against that page instead of the real match count.

Send status, author, and limit as query params, read the server's total for the shown/total display, and drop the client-side filter/sort/limit machinery. --limit above 200 is clamped with a note when matches exceed the page. The grouped-by-status view is replaced by a flat list with a STATUS column whenever more than one status can appear, so unknown server statuses stay visible without aggregation.

findTrail (trail show/update lookups) had the same first-page blindness; as a stopgap it now requests the 200-row server max.