[Parent] Consolidate frontend review lifecycle orchestration

[jenul-ferdinand]

What

Create one frontend Review module for create, edit, delete, reaction transitions, current-user synchronization, and refresh behaviour.

Why

Unit Overview, User Profile, and Review Card coordinate review requests, toast messages, current-user updates, refresh signals, optimistic reaction updates, and rollback behaviour. The operation-specific transport modules leave this lifecycle knowledge in each caller.

Area

• frontend

Implementation issues

• Centralize review create, edit, and delete lifecycle #261 Centralize review create, edit, and delete lifecycle
• Centralize review reaction state transitions #262 Centralize review reaction state transitions

Notes or constraints

• Keep this issue frontend-only. Do not change backend contracts.
• Keep editor and card rendering in their existing route modules.

Done when

• Callers do not coordinate review mutation ordering or session synchronization.
• One Review module owns optimistic reaction transitions and rollback.
• Tests exercise the review lifecycle through its interface.