chore: update cloudly dependency stack

Align Cloudly with the current typedserver, smartconfig, smartstate, and Docker tooling releases so builds and Docker output stay compatible with the upgraded stack.

ts/manager.settings/classes.settingsmanager.ts

@@ -5,7 +5,7 @@ import * as servezoneInterfaces from '@serve.zone/interfaces';
 export class CloudlySettingsManager {
   public cloudlyRef: Cloudly;
   public readyDeferred = plugins.smartpromise.defer();
-  public settingsStore: plugins.smartdata.EasyStore<servezoneInterfaces.data.ICloudlySettings>;
+  public settingsStore!: plugins.smartdata.EasyStore<servezoneInterfaces.data.ICloudlySettings>;
   
   constructor(cloudlyRefArg: Cloudly) {
     this.cloudlyRef = cloudlyRefArg;
@@ -196,7 +196,7 @@ export class CloudlySettingsManager {
           return { success: false, message: `Unknown provider: ${provider}` };
       }
     } catch (error) {
-      return { success: false, message: `Connection test failed: ${error.message}` };
+      return { success: false, message: `Connection test failed: ${error instanceof Error ? error.message : String(error)}` };
     }
   }
 
@@ -232,9 +232,10 @@ export class CloudlySettingsManager {
               message: 'Settings updated successfully'
             };
           } catch (error) {
+            const errorMessage = error instanceof Error ? error.message : String(error);
             return {
               success: false,
-              message: `Failed to update settings: ${error.message}`
+              message: `Failed to update settings: ${errorMessage}`
             };
           }
         }
@@ -254,9 +255,10 @@ export class CloudlySettingsManager {
               message: `Setting ${requestData.key} cleared successfully`
             };
           } catch (error) {
+            const errorMessage = error instanceof Error ? error.message : String(error);
             return {
               success: false,
-              message: `Failed to clear setting: ${error.message}`
+              message: `Failed to clear setting: ${errorMessage}`
             };
           }
         }