feat(smart-app): implement complete mobile app MVP

- App.tsx: full navigation (Auth stack + Main tabs with 5 screens)
- Auth: LoginScreen, RegisterScreen, ForgotPasswordScreen
- HomeScreen: dashboard with IoT metrics, weather widget, alerts, quick actions, sensors
- MapScreen: interactive map with layer toggles (6 layers)
- MarketplaceScreen: categories (6), products (5), search
- ChatScreen: AI chat with quick prompts (4), bot responses
- ProfileScreen: user info, stats, menu (9 items), logout
- AlertsScreen: alert list with severity, acknowledge
- SensorsScreen: sensor list with type filters (6 types), search
- ZonesScreen: zone cards with stats
- SettingsScreen: language picker (FR/EN/ES/DE), privacy, about
- Stores: iotStore (sensors, zones, alerts), notificationStore, uiStore + i18n
- Hooks: useSensors, useAlerts, useNotifications, useLocation
- Components: Card, Button, LoadingSpinner, ErrorBoundary, Header
- Services: iotService, notificationService (with axios API client)
- Utils: formatters (temp, AQI, noise, dates), validators (email, password, IBAN)
- Theme: colors.ts with full design system (Blue Ocean palette)
- Ditto: fixed MongoDB connection, new JWT secrets, official gateway image

smart-app-city/frontend/node_modules/react-native/Libraries/Interaction/FrameRateLogger.js

@@ -0,0 +1,72 @@
+/**
+ * Copyright (c) Meta Platforms, Inc. and affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ *
+ * @format
+ * @flow strict-local
+ */
+
+import NativeFrameRateLogger from './NativeFrameRateLogger';
+
+const invariant = require('invariant');
+
+/**
+ * Flow API for native FrameRateLogger module. If the native module is not installed, function calls
+ * are just no-ops.
+ *
+ * Typical behavior is that `setContext` is called when a new screen is loaded (e.g. via a
+ * navigation integration), and then `beginScroll` is called by `ScrollResponder` at which point the
+ * native module then begins tracking frame drops. When `ScrollResponder` calls `endScroll`, the
+ * native module gathers up all it's frame drop data and reports it via an analytics pipeline for
+ * analysis.
+ *
+ * Note that `beginScroll` may be called multiple times by `ScrollResponder` - unclear if that's a
+ * bug, but the native module should be robust to that.
+ *
+ * In the future we may add support for tracking frame drops in other types of interactions beyond
+ * scrolling.
+ */
+const FrameRateLogger = {
+  /**
+   * Enable `debug` to see local logs of what's going on.
+   */
+  setGlobalOptions: function (options: {debug?: boolean, ...}) {
+    if (options.debug !== undefined) {
+      invariant(
+        NativeFrameRateLogger,
+        'Trying to debug FrameRateLogger without the native module!',
+      );
+    }
+    NativeFrameRateLogger?.setGlobalOptions({
+      debug: !!options.debug,
+    });
+  },
+
+  /**
+   * Must call `setContext` before any events can be properly tracked, which is done automatically
+   * in `AppRegistry`, but navigation is also a common place to hook in.
+   */
+  setContext: function (context: string) {
+    NativeFrameRateLogger?.setContext(context);
+  },
+
+  /**
+   * Called in `ScrollResponder` so any component that uses that module will handle this
+   * automatically.
+   */
+  beginScroll() {
+    NativeFrameRateLogger?.beginScroll();
+  },
+
+  /**
+   * Called in `ScrollResponder` so any component that uses that module will handle this
+   * automatically.
+   */
+  endScroll() {
+    NativeFrameRateLogger?.endScroll();
+  },
+};
+
+module.exports = FrameRateLogger;