fix: ensure intl polyfills load before runtime config

- Added name to load-intl-polyfills initializer
- Made load-runtime-config run after load-intl-polyfills
- Fixes race condition where intl service initialized before polyfill data loaded
- Resolves MISSING_DATA errors for all locales (mn-mn, etc.)

Initialization order now:
1. load-intl-polyfills (loads formatjs polyfill data)
2. load-runtime-config (loads fleetbase.config.json)
3. load-socketcluster-client
4. Other initializers

console/app/initializers/load-intl-polyfills.js

@@ -38,4 +38,7 @@ export function initialize(application) {
     })();
 }
 
-export default { initialize };
+export default {
+    name: 'load-intl-polyfills',
+    initialize
+};

console/app/initializers/load-runtime-config.js

@@ -35,6 +35,7 @@ export function initialize(application) {
 export default {
     name: 'load-runtime-config',
     initialize,
-    // Run before everything else
+    // Run after intl polyfills are loaded, before socketcluster
+    after: 'load-intl-polyfills',
     before: 'load-socketcluster-client'
 };