fix(task) #25 RequestTask fails the task when the SOAP call fails

[njoubert-cleverage]

Description

Fixes #25.

When a SOAP call failed, RequestTask applied the error strategy itself: with stop, it stopped the process without setting an exception, so the process was not failed and the console command exited 0; with skip, the error outputs received false.

• RequestTask::execute(): after logging the failed call (with the last request and response), throw a RuntimeException (Soap call '<method>' on client '<client>' failed), handled by the process manager like any other task error
• RequestTaskTest (new): a successful call is output; a failed call throws without setting any output, error output or stopped flag (fails without the fix)
• request_task.md, soap_enrich_csv.md cookbook: document the new behaviour

Checked in process-bundle-demo with a client pointing to a closed port:

• demo.soap.call_failure (stop): the process fails, exit code 1 (executed successfully, exit code 0 before)
• demo.soap.call_failure_skip (skip): the error outputs receive the task input (false before)

Requirements

• Documentation updates
  • Reference
  • Cookbooks
  • Changelog
• Unit tests

Breaking changes

• With the stop strategy, a failed call now fails the process (non-zero exit code).
• With the skip strategy, the error outputs receive the task input instead of false.

🤖 Generated with Claude Code