Create @apps/ui-staff bootstrap app and compose initial staff route packages

[nnoce14]

Summary

Create the initial @apps/ui-staff application as a thin bootstrap/composition shell, consistent with the route-package architecture being adopted for @apps/ui-community.

The app should own application bootstrapping concerns only, such as router composition, providers, auth wiring, and top-level layout composition. Feature/layout route implementations should live in @ocom packages.

Scope

Create:

• @apps/ui-staff
• route composition for initial staff sections
• shared app bootstrap wiring needed to host the route packages

Add initial package references for:

• @ocom/ui-staff-route-root
• @ocom/ui-staff-route-community-management
• @ocom/ui-staff-route-user-management
• @ocom/ui-staff-route-finance
• @ocom/ui-staff-route-tech-admin
• @ocom/ui-staff-shared

Requirements

• keep @apps/ui-staff thin
• no business UI implementation directly in the app shell except minimal composition glue
• establish top-level route structure for unauthenticated/authenticated staff flows
• provide a clear route for unauthorized access handling
• follow existing repo conventions for app/package setup

Suggested App route shape

• /
• /auth-redirect
• /staff/...

Top-level authenticated sections should be composed under the staff area.

Acceptance criteria

• @apps/ui-staff exists and builds
• app shell composes the new route packages cleanly
• no section-specific feature implementation is embedded directly in the app shell
• route structure is in place for root/login, communities, finance, and tech admin sections
• unauthorized route handling is present