3.29.0

Included commits: 3.28.0...3.29.0

Improvements

• Made backend gateway request exception messages actionable by introducing AbstractHttpClient::buildRequestExceptionMessage(), which reports the exact request target and HTTP method, the response status (flagging proxy statuses such as 502/503/504 as not reaching the gateway application), the X-Request-ID header value to correlate the record with the gateway's own log, and the gateway response body instead of a generic Stacktrace: label.
• Adjusted InvalidZedResponseException to include the X-Request-ID value and a more descriptive raw body excerpt (explicitly noting an empty body or a truncated body with total size) so the thrown exception message is actionable for investigation.
• Changed InvalidZedResponseException::__construct() to accept an optional $requestId parameter to carry the request id used to correlate log records with the backend gateway's log.

Deprecations

• Deprecated AbstractHttpClient::ZED_REQUEST_ERROR in favor of AbstractHttpClient::ZED_REQUEST_ERROR_TEMPLATE, since the old template mislabeled the appended gateway response body as a stacktrace and omitted both the response status code and the request id needed to find the matching record in the gateway's own log.