feat: Improve Redis startup handling in install script

- Handle Redis startup differently for GitHub Actions on macOS:
  Start redis directly instead of relying on `brew services`.
- Improved error handling for redis start failures.
- Enhanced logging for better troubleshooting.

install_v.sh

@@ -375,12 +375,30 @@ check_and_start_redis() {
             fi
         fi
     elif [[ "${OSNAME}" == "darwin"* ]]; then
+        # Check if we're in GitHub Actions
+        if is_github_actions; then
+            echo "Running in GitHub Actions on macOS. Starting redis directly..."
+            if pgrep redis-server > /dev/null; then
+                echo "redis is already running."
+            else
+                echo "redis is not running. Starting it in the background..."
+                redis-server --daemonize yes
+                if pgrep redis-server > /dev/null; then
+                    echo "redis started successfully."
+                else
+                    echo "Failed to start redis. Please check logs for details."
+                    exit 1
+                fi
+            fi
+        else
+            # For regular macOS environments, use brew services
             if brew services list | grep -q "^redis.*started"; then
                 echo "redis is already running."
             else
                 echo "redis is not running. Starting it..."
                 brew services start redis
             fi
+        fi
     elif [[ "${OSNAME}" == "alpine"* ]]; then
         if rc-service "redis" status | grep -q "running"; then
             echo "redis is already running."