fix: [#14] eliminate sudo prompts in CI tests

- Update provision-infrastructure test to use invalid environment parameter
- Prevents script from reaching sudo caching logic during CI testing
- Test now fails early during parameter validation instead of at infrastructure stage
- Maintains error handling test coverage without requiring interactive sudo prompts

Problem:
- make test-ci was prompting for sudo password when cache expired
- Caused by test calling provision-infrastructure.sh with parameters that trigger apply action
- Apply action requires sudo for libvirt operations via ensure_sudo_cached()

Solution:
- Changed test to use 'invalid-env' parameter instead of 'local'
- Script fails during environment validation before reaching sudo logic
- CI tests now run completely non-interactively

Benefits:
- CI tests run without user interaction
- Faster test execution (3s vs 19s)
- Maintains test validation of error handling behavior
- Clean separation between CI tests and system operations

Author: josecelano

infrastructure/tests/scripts/test-provision-infrastructure.sh

@@ -71,11 +71,11 @@ test_provision_infrastructure_error_handling() {
         log_success "Script properly handles missing parameters"
     fi
 
-    # Test with insufficient parameters
-    if "${SCRIPT_PATH}" "local" >/dev/null 2>&1; then
-        log_warning "Script should fail with insufficient parameters"
+    # Test with insufficient parameters (invalid environment to avoid sudo)
+    if "${SCRIPT_PATH}" "invalid-env" >/dev/null 2>&1; then
+        log_warning "Script should fail with invalid environment"
     else
-        log_success "Script properly handles insufficient parameters"
+        log_success "Script properly handles invalid environment"
     fi
 
     return ${failed}