fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534)

~1500 progress messages across 481 files were using log_warn (yellow)
for normal status updates like "Installing...", "Setting up...",
"Creating server...", etc. This made users think something was wrong
when everything was proceeding normally.

Changes:
- Replace log_warn with log_step for all progress/status messages
- Keep log_warn only for actual warnings (errors, remediation hints)
- Remove emoji from 3 sprite completion messages

Agent: ux-engineer

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>

binarylane/aider.sh

@@ -20,7 +20,7 @@ create_server "${SERVER_NAME}"
 verify_server_connectivity "${BINARYLANE_SERVER_IP}"
 wait_for_cloud_init "${BINARYLANE_SERVER_IP}" 60
 
-log_warn "Installing Aider..."
+log_step "Installing Aider..."
 run_server "${BINARYLANE_SERVER_IP}" "pip install aider-chat 2>/dev/null || pip3 install aider-chat"
 
 if ! run_server "${BINARYLANE_SERVER_IP}" "command -v aider &> /dev/null && aider --version &> /dev/null"; then
@@ -38,7 +38,7 @@ fi
 
 MODEL_ID=$(get_model_id_interactive "openrouter/auto" "Aider") || exit 1
 
-log_warn "Setting up environment variables..."
+log_step "Setting up environment variables..."
 inject_env_vars_ssh "${BINARYLANE_SERVER_IP}" upload_file run_server \
     "OPENROUTER_API_KEY=${OPENROUTER_API_KEY}"
 
@@ -47,7 +47,7 @@ log_info "BinaryLane server setup completed successfully!"
 log_info "Server: ${SERVER_NAME} (ID: ${BINARYLANE_SERVER_ID}, IP: ${BINARYLANE_SERVER_IP})"
 echo ""
 
-log_warn "Starting Aider..."
+log_step "Starting Aider..."
 sleep 1
 clear
 interactive_session "${BINARYLANE_SERVER_IP}" "source ~/.zshrc && aider --model openrouter/${MODEL_ID}"