Resolve #3613841 "Make the personal task and request views usable in place of the pages they mirror"

Fixes the three things that stopped the shipped personal Views from replacing the pages they mirror.

The act link missed whole task families. TaskActLink asked the task type plugin for a route and skipped anything not implementing TaskActRouteInterface — which is an implementation detail of InboxTaskHandler, not the seam a family declares its act surface through. An interaction task reaches its surface through its own handler, so the inbox page linked it and the view rendered an empty string. Both act links now resolve through PendingActionHandlerInterface::actUrl() and thread the listing on as the return target.

A row offered no actions. The inbox's link building moved into orchestra_inbox.task_actions, and both the inbox page and the new Operations field build from it, so they cannot drift. Same guards: claim only for an unassigned open task, release only for a claimed pooled task, guarded outcomes withheld.

Neither row had a layout. One shared card row (orchestra-card-row.html.twig) is included by every personal list, on a card component promoted into the base module. That component also styles the status tag orchestra_views already rendered, whose stylesheet lived in orchestra_ui — a module it does not depend on, so the tag was unstyled unless the requester UI happened to be enabled.

PendingActionsFinder moved to the base module, where its eight dependencies already lived, so the requester view can offer the step waiting on the viewer through the same finder the themed page uses. Its service id is now orchestra.pending_actions.

Also in: the labeled fields the pages show and the views did not (task state, run reference falling back to the run id, the outcome as its authored label, who holds a task); the authored status as its tag with the engine state beneath it as the lifecycle marker; per-step CSS classes on every control offered for a step, so a design can give one step its own icon without replacing a template; and the shipped view labels added to the .po files, where none of them were present.

Tests: 41 kernel classes across orchestra_inbox, orchestra_views, orchestra_ui and orchestra_interaction_operation pass, including a new test module whose task family ships a handler and declares no act route — the shape the old code rendered nothing for.

Consumers: the finder's service id changed, so yoyaku_orchestra_order needs the matching one-line update (filed separately).