fix(app): clear selection after manual flow

[kropsi]

Scope

What's changed:

• Restored selection clear after a manual flow runs from the collection list view sidebar (regressed in Add use-flows composable and refactored flow-sidebar-detail manual flow logic #25962 /
  v11.13.0)
• Selection is cleared after the trigger request resolves; if the trigger request itself fails (network / 4xx / 5xx) the
  selection is preserved so the user can retry. Note: this matches what the trigger endpoint reports — operation-level
  rejections inside the flow still return HTTP 200, so they are treated as success here, same as pre-v11.13.0 behavior
• Added two unit tests covering the new behavior

Potential Risks / Drawbacks

• None identified — single-line additive change on the success path, gated by the existing try

Tested Scenarios

• Manual flow with selection on collection list view → selection cleared after the trigger request resolves
• Trigger request rejection (mocked) → selection preserved (user can retry)
• Existing 15 tests in use-flows.test.ts continue to pass; full suite is 17/17
• Manual end-to-end test against a local Directus instance (sqlite, seeded test_items collection, manual flow with
  requireSelection: true) confirmed the clear

Review Notes / Questions

• The fix mirrors the pre-v11.13.0 ordering from batchRefresh in collection.vue: clear, then refresh
• Placed inside useFlows rather than each caller's onRefreshCallback, since the composable owns the selection ref
• On the item view, selection defaults to an empty ref in useFlows, so the new line is a no-op there
• keys for the API call is captured before the clear, so the trigger still uses the right selection

Checklist

• Added or updated tests
• Documentation PR created here or not required
• OpenAPI package PR created here or not required

---

Fixes #27323

[rijkvanzanten]

LGTM!

[AlexGaillard]

Great turn around time 👍 🚀 Thanks @kropsi 😄 and congrats on contrib