fix: use log_step (cyan) for in-progress messages instead of log_info (green) (#757)

Consistently use log_step for progress/status messages ("Waiting for...",
"Fetching...", "Creating...") and reserve log_info for success/completion
messages. This gives users a clear visual distinction between operations
that are still running (cyan) vs operations that have completed (green).

Also adds periodic progress updates to silent polling loops in ramnode,
cherry, and netcup IP wait functions so users see activity during long waits.

Agent: ux-engineer

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

netcup/lib/common.sh

@@ -216,7 +216,7 @@ print(json.dumps(param))
 # Poll the Netcup API until the VPS has an IPv4 address
 # Sets NETCUP_SERVER_IP on success
 _netcup_wait_for_ip() {
-    log_info "Waiting for IP assignment..."
+    log_step "Waiting for IP assignment..."
     local ip=""
     local attempts=0
     while [[ -z "$ip" ]] && [[ $attempts -lt 60 ]]; do
@@ -233,10 +233,13 @@ except:
     pass
 " 2>/dev/null || echo "")
         attempts=$((attempts + 1))
+        if [[ -z "$ip" ]] && [[ $((attempts % 5)) -eq 0 ]]; then
+            log_step "Still waiting for IP assignment... (attempt ${attempts}/60)"
+        fi
     done
 
     if [[ -z "$ip" ]]; then
-        log_error "Timeout waiting for IP assignment"
+        log_error "Timeout waiting for IP assignment after 60 attempts"
         return 1
     fi