fix: handle :system_not_started error in cluster restart

When Ra system hasn't been initialized on a node yet, :ra.stop_server
returns {:error, :system_not_started} which wasn't being handled,
causing a TryClauseError.

Added case clause to handle :system_not_started and skip the stop
operation gracefully. The start_server call will still work to
initialize the cluster.

Author: GSMLG-BOT

scripts/cluster_connect.exs

@@ -62,6 +62,9 @@ defmodule ClusterHelper do
       {:error, :not_started} ->
         IO.puts("⚠ Ra server was not started")
 
+      {:error, :system_not_started} ->
+        IO.puts("⚠ Ra system not started yet, skipping stop")
+
       error ->
         IO.puts("⚠ Stop server returned: #{inspect(error)}")
     end