fix(settings): streamline settings type creation in settingsService and initialization

- Refactored settingsService to use findOrCreate for settings type, improving efficiency and error handling.
- Added initialization for 'account' settings type in initializeSettings, ensuring all necessary settings are created during setup.

backend/services/settingsService.js

@@ -42,12 +42,10 @@ class SettingsService extends BaseService{
             return null;
         }
 
-        const settingsType = await SettingsType.findOne({
+        const [settingsType] = await SettingsType.findOrCreate({
-            where: { name: definition.setting }
+            where: { name: definition.setting },
+            defaults: { name: definition.setting }
         });
-        if (!settingsType) {
-            throw new Error(`Missing settings type: ${definition.setting}`);
-        }
 
         const [paramType] = await UserParamType.findOrCreate({
             where: { description },

backend/utils/initializeSettings.js

@@ -17,6 +17,10 @@ const initializeSettings = async () => {
         where: { name: 'flirt' },
         defaults: { name: 'flirt' }
     });
+    await SettingsType.findOrCreate({
+        where: { name: 'account' },
+        defaults: { name: 'account' }
+    });
     await SettingsType.findOrCreate({
         where: { name: 'languageAssistant' },
         defaults: { name: 'languageAssistant' }