[UI] Staff simplified navigation (Phase 9/10)

[CRamsan]

Phase 9/10 — Staff Simplified Navigation

Implement role-differentiated bottom navigation for Staff users. This is split from #408 (Resident Experience) where SET-08 was misplaced, and from #409 (Settings & Profile).

Scope

Staff-role users see a navigation bar optimized for their primary workflow:

Item	Route
Dashboard	Route.Dashboard
Tasks	Route.TaskList
Properties	Route.PropertyList
More	Route.Settings

Admin/Owner users retain their current navigation ordering.

Implementation

• Implement as a configuration-driven nav item list based on the current user's role from SessionManager
• Preferred: single BottomNavBar composable that accepts a List<BottomNavItem> and a role-keyed factory function that produces the correct list
• Alternative: separate Staff and Admin/Owner composables
• Role derived from shared SessionManager or OrgContext injected via Koin — do not pass role as a nav argument

Dependencies

• [UI] Settings + Profile — Edit Profile, Team Management refactor (Phase 10) #409 — Settings & Profile (Settings screen must exist as a nav target)
• [UI] Dashboard screen — property count, pending tasks, recent activity (Phase 2) #395 — Dashboard (must exist as a nav target)
• [UI] Refactor Event Log into typed views: Task List, Guest Log, Maintenance (Phase 4) #400 — Task List (must exist as a nav target)

What type of task is this?

Development