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/babel-core/README.md

@@ -0,0 +1,50 @@
+## babel-bridge
+
+This repo holds what we're calling a "bridge" package that is meant to ease the
+transition for libraries that use "babel-core" as a peer dependency for Babel 6.
+
+The issue with Babel 7's transition to scopes is that if a package depends on
+Babel 6, they may want to add support for Babel 7 alongside. Because Babel 7
+will be released as `@babel/core` instead of `babel-core`, maintainers have
+no way to do that transition without making a breaking change. e.g.
+
+```js
+peerDependencies: {
+  "babel-core": "6.x"
+}
+```
+cannot change to
+
+```js
+peerDependencies: {
+  "@babel/core": "6.x"
+}
+```
+
+without it being a breaking change.
+
+### Solution
+
+To address this, we're releasing this bridge package, to allow users to do
+
+
+```js
+peerDependencies: {
+  "babel-core": "6.x | ^7.0.0-bridge"
+}
+```
+
+then where users of this package would originally have done
+
+```sh
+npm i some-package babel-core
+```
+
+to install Babel 6, they could now do
+
+
+```sh
+npm i some-package babel-core@^7.0.0-bridge @babel/core
+```
+
+to install the bridge package, and install Babel 7's core.