fix(task) #29 #30 #31 #32 #33 SOAP options and headers per call, SoapFault handling, input check; #23 add missing tests

[njoubert-cleverage]

Description

Fixes #23.
Fixes #29.
Fixes #30.
Fixes #31.
Fixes #32.
Fixes #33.

Grouped in one PR because the fixes change the same task, transformer, client, tests, reference pages and the CHANGELOG Latest section.

SOAP options and headers per call (#29, #30)

• SoapCallOptionsTrait (new), used by RequestTask and RequestTransformer: the soap_call_options / soap_call_headers options (and the header normalizer, moved from the task), and callWithSoapOptions(), which sets the given options / headers on the client for the call only, then restores the previous ones (also after a failure).
• RequestTask: the options / headers of the client definition (calls: [setSoapHeaders, ...]) are no longer overwritten by null (RequestTask overwrites the SOAP options and headers of the client definition #29), and the task ones no longer leak to the next calls of the client (SOAP options and headers of a RequestTask leak to the next calls of the client #30).
• RequestTransformer (soap_request): new soap_call_options / soap_call_headers options (SOAP options and headers of a RequestTask leak to the next calls of the client #30).

SOAP faults (#31, #32)

• Client::doSoapCall() rethrows the SoapFault after logging it (it returned false), and handles a SoapFault returned with exceptions: false the same way (SOAP faults are output as results with the exceptions: false option #32).
• RequestTask catches the SoapFault: same error log (Empty resultset for query, now with the fault message) and same RuntimeException, with the fault as previous exception. A method returning false now outputs false (A SOAP method returning false is handled as a failed call #31).
• RequestTransformer throws a RuntimeException on a SoapFault (it returned false).

Input (#33): RequestTask throws RequestTask expects an array or empty input, <type> given (TypeError from Client::call()); Client::call() logs the notice before a soapCall<Method>() override.

Tests (#23)

• FakeSoapClient (test helper): a non-WSDL SoapClient answering prepared responses through __doRequest(), without network access (signature compatible from PHP 8.2 to 8.5).
• ClientTest, RequestTransformerTest, MissingClientExceptionTest, CleverAgeSoapProcessExtensionTest, CleverAgeSoapProcessBundleTest (new); RequestTaskTest rewritten with a real Client: results (including false), headers / options of the client kept, task ones sent for the call only and restored, faults, exceptions: false, overrides, input, header options.

Coverage: 172/172 lines (32 tests). Without the fix, 10 of the tests fail. The bundle test declares every class it runs (RegisterClientsPass included, unlike the rest bundle where it made main fail).

Documentation: request_task.md, request_transformer.md (new options, failures), client.md (failures, exceptions: false, shared state, override example).

Checked with process-bundle-demo and a SOAP service mocked by WireMock (see the demo PR):

Process	Before	After
demo.soap.client_headers (header from the client definition)	"count" : 0	"count" : 1
demo.soap.headers_leak (task header, then soap_request)	"count" : 2	"count" : 1
demo.soap.false_result	Soap call 'IsAvailable' on client 'wiremock' failed	false
demo.soap.fault_without_exceptions	SoapFault object output	fails
demo.soap.invalid_input	TypeError	RequestTask expects an array or empty input, string given
demo.soap, demo.soap.call_failure, demo.soap.call_failure_skip		unchanged

Not changed: the Empty resultset for query error message (misleading, but used by the documentation and the cookbook).

Requirements

• Documentation updates
  • Reference
  • Changelog
• Unit tests

Breaking changes

• RequestTask overwrites the SOAP options and headers of the client definition #29 / SOAP options and headers of a RequestTask leak to the next calls of the client #30: the options / headers of the client definition are sent when the task does not set its own; the task ones are no longer reused by the next calls.
• A SOAP method returning false is handled as a failed call #31: a false result is output (the task failed); the soap_request transformer throws on a SoapFault (it returned false); Client::doSoapCall() (protected) throws the SoapFault instead of returning false, so a custom soapCall<Method>() returning false no longer makes the task fail.
• SOAP faults are output as results with the exceptions: false option #32: a SOAP fault makes the call fail whatever the exceptions option.

🤖 Generated with Claude Code