Link the Retention, Execution and Versions pages from the workflow operations

Problem

A workflow's Retention, Execution and Versions pages can only be reached by typing their path. Their tabs declare the workflow canonical page as base route, but that page is served by the modeler view, which renders no local tasks, so the tabs never appear there; and the model list has no operation linking to those pages.

Proposed resolution

orchestra_ui's hook_entity_operation adds Retention, Execution and Versions operations to each workflow on the model list, next to the existing Start. Ordering is improved: Start (the primary runtime action) sits just under Edit, and the three configuration pages group together at the end, before Delete. Core access-checks each operation route, so a user without the administer permission sees only the operations they may use.

The operations kernel test is extended (renamed to WorkflowOperationsTest) to assert each operation is present and routed correctly.