Issue a PUT request after a GET request responding with 202 and a Location header

[aslakhellesoy]

The https://messages.cucumber.io service responds with 413 Payload Too Large for message files larger than 6 Mb. This was discovered during a chat with one of our users.

We've adopted the solution outlined in Option 2 in this blog post. A GET https://messages.cucumber.io/api/reports request will now respond with 202 Accepted and a Location header pointing to S3.

This is not a proper redirect, so we're handling this in the code by issuing a new PUT request if the status is 202 and the Location header is present.

This change preserves backwards compatibility for all HTTP verbs except GET. However, this change in behaviour will only manifest itself for users issuing GET request to servers expecting a body in the request, which is legal, but not useful. We don't expect anyone to be affected.

For this reason we consider this change to be an addition, which should trigger a minor release.

The same change has been applied to Ruby.

[coveralls]

Coverage decreased (-0.0004%) to 86.181% when pulling 7bfddc0 on get-put-redirect into 402ce89 on main.

[mpkorstanje]

For future consideration, it might be worth removing the UrlOutputstream from all formatters except the publish formatter. It's becoming quite protocol specific.