ext/soap: Use more accurate return types in implementations of SoapClient::__doRequest()

The do_request() function that calls this methods, assumes that a string is being returned from the m

ext/soap: Use more accurate return types in implementations of SoapClient::__doRequest()

The do_request() function that calls this methods, assumes that a string is being returned from the method
otherwise it bails out.

However, the default implementation of SoapClient::__doRequest() indicates that it can return null when it
fails to set-up and execute the HTTP SOAP request, but this always results in a SoapFault exception being
thrown, and thus cannot happen in practice.

We need to investigate further if the return type should be changed from ?string to string or not.

show more ...

EXPECTFize ext/soap tests where exact object IDs are displayed

These cause test failures when we migrate resources to objects. But anyway, hardcoding the object IDs and the number of propert

EXPECTFize ext/soap tests where exact object IDs are displayed

These cause test failures when we migrate resources to objects. But anyway, hardcoding the object IDs and the number of properties is hardly ever useful, so it's fine to get rid of them.
Related to #14121

show more ...

Fix segfault and assertion failure with refcounted props and arrays

Closes GH-12478.

Fix segfault and assertion failure with refcounted props and arrays

Closes GH-12478.