fix: [#14] correct configure-env test logic to eliminate CI warning

The test was incorrectly expecting the configure-env.sh script to fail
when called without parameters, but the script is designed to use
sensible defaults ('local' environment).

Changes:
- Fixed test logic to expect success when script uses defaults
- Replaced warning message with proper success validation
- Added proper error handling when script actually fails

This eliminates the CI warning:
'[WARNING] Script should handle missing parameters gracefully'

The script DOES handle missing parameters gracefully by using defaults,
so the test should validate this behavior correctly.

Author: josecelano

infrastructure/tests/scripts/test-configure-env.sh

@@ -63,11 +63,12 @@ test_configure_env_error_handling() {
     # Test with invalid environment names
     log_info "Testing invalid environment handling..."
 
-    # Test with empty parameters
+    # Test with empty parameters - script should succeed with defaults
     if "${SCRIPT_PATH}" >/dev/null 2>&1; then
-        log_warning "Script should handle missing parameters gracefully"
+        log_success "Script properly handles missing parameters by using defaults"
     else
-        log_info "Script properly handles missing parameters"
+        log_error "Script failed when it should use default parameters"
+        failed=$((failed + 1))
     fi
 
     log_success "Configuration script error handling tests completed"