client: add info from http response to client exception

[davidjgoss]

Problem

When using the HttpTransport with the Java client, if the receiving service (Marquez or whatever) responds with a non-2xx status then an OpenLineageClientException is thrown with a descriptive message. The consuming code may want to do something different with that exception depending on the response - e.g. we might retry the operation for a 502 but not for a 400. Currently this information has to be parsed out of the exception message.

Solution

This PR adds HttpTransportResponseException, a subclass of OpenLineageClientException that includes fields for status code and body - this is what is now thrown in the event of a non-2xx response. Note that other exception-raising scenarios like timeouts and bad config will behave as previously. Also, the message on the exception remains the same for backwards compatibility.

One-line summary:

Adds the status code and body as properties on the thrown exception when a non-success response is encountered in the HTTP transport.

Checklist

• You've signed-off your work
• Your pull request title follows our guidelines
• Your changes are accompanied by tests (if relevant)
• Your change contains a small diff and is self-contained
• You've updated any relevant documentation (if relevant)
• Your comment includes a one-liner for the changelog about the specific purpose of the change (if necessary)
• You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
• You've added a header to source files (if relevant)

---

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project

[pawel-big-lebowski]

Looks good to me.

Minor: wouldn't HttpTransportResponseException constructor be a better place to create message?

[davidjgoss]

Minor: wouldn't HttpTransportResponseException constructor be a better place to create message?

Good point, have done that.