feat: Migrate staff profile features from Data Connect to V2 REST API

- Removed data_connect package from mobile pubspec.yaml.
- Added documentation for V2 profile migration status and QA findings.
- Implemented new session management with ClientSessionStore and StaffSessionStore.
- Created V2SessionService for handling user sessions via the V2 API.
- Developed use cases for cancelling late worker assignments and submitting worker reviews.
- Added arguments and use cases for payment chart retrieval and profile completion checks.
- Implemented repository interfaces and their implementations for staff main and profile features.
- Ensured proper error handling and validation in use cases.

.claude/agents/mobile-architecture-reviewer.md

@@ -26,6 +26,7 @@ and load any additional skills as needed for specific review challenges.
 - Ensuring business logic lives in use cases (not BLoCs/widgets)
 - Flagging design system violations (hardcoded colors, TextStyle, spacing, icons)
 - Validating BLoC pattern usage (SessionHandlerMixin, BlocErrorHandler, singleton registration)
+- **Verifying every feature module that uses `BaseApiService` (or any CoreModule binding) declares `List<Module> get imports => <Module>[CoreModule()];`** — missing this causes `UnregisteredInstance` runtime crashes
 - Ensuring safe navigation extensions are used (no direct Navigator usage)
 - Verifying test coverage for business logic
 - Checking documentation on public APIs
@@ -205,6 +206,7 @@ Produce a structured report in this exact format:
 |------|--------|---------|
 | Design System | ✅/❌ | [details] |
 | Architecture Boundaries | ✅/❌ | [details] |
+| DI / CoreModule Imports | ✅/❌ | [Every module using BaseApiService must import CoreModule] |
 | State Management | ✅/❌ | [details] |
 | Navigation | ✅/❌ | [details] |
 | Testing Coverage | ✅/❌ | [estimated %] |