feat: Update API endpoint usage in repositories to remove redundant path property

- Refactored multiple repository implementations across client and staff features to directly use endpoint objects without accessing the `path` property.
- Introduced a new `FeatureGate` class for client-side feature gating based on user scopes, allowing for better access control to API endpoints.
- Added `ApiEndpoint` class to represent API endpoints with their paths and required scopes for future feature gating.

apps/mobile/packages/features/client/home/lib/src/data/repositories_impl/home_repository_impl.dart

@@ -18,7 +18,7 @@ class HomeRepositoryImpl implements HomeRepositoryInterface {
   @override
   Future<ClientDashboard> getDashboard() async {
     final ApiResponse response =
-        await _apiService.get(ClientEndpoints.dashboard.path);
+        await _apiService.get(ClientEndpoints.dashboard);
     final Map<String, dynamic> data = response.data as Map<String, dynamic>;
     return ClientDashboard.fromJson(data);
   }
@@ -26,7 +26,7 @@ class HomeRepositoryImpl implements HomeRepositoryInterface {
   @override
   Future<List<RecentOrder>> getRecentReorders() async {
     final ApiResponse response =
-        await _apiService.get(ClientEndpoints.reorders.path);
+        await _apiService.get(ClientEndpoints.reorders);
     final Map<String, dynamic> body = response.data as Map<String, dynamic>;
     final List<dynamic> items = body['items'] as List<dynamic>;
     return items