Centralize review create, edit, and delete lifecycle

[jenul-ferdinand]

What

Move review creation, editing, deletion, current-user review-ID synchronization, and refresh behaviour into the frontend Review module.

Why

Unit Overview and User Profile repeat mutation ordering, toast handling, current-user updates, and refresh signals. Each caller must understand the same lifecycle.

Area

• frontend

Parent tracking issue

• [Parent] Consolidate frontend review lifecycle orchestration #258 Consolidate frontend review lifecycle orchestration

Notes or constraints

• Keep editor and route rendering where they are.
• Keep backend contracts unchanged.
• Migrate Unit Overview and User Profile after the Review module owns the lifecycle.
• Test successful and failed mutations and displayed-review synchronization.

Done when

• Route modules do not coordinate review mutation ordering or current-user review IDs.
• The Review module exposes the lifecycle test surface.