Filter out retry events for progress bar assertion on intg tests

[RanVaknin]

Our S3 transfer manager integ test has a progress bar assertion that is intermittently failing due to an unaccounted retry message.

[ERROR] software.amazon.awssdk.transfer.s3.progress.LoggingTransferListenerTest.test_customTicksListener_successfulTransfer -- Time elapsed: 0.027 s <<< FAILURE!
org.opentest4j.AssertionFailedError:

expected: "|==== | 80.0%"
but was: "Retrying Request: DefaultSdkHttpFullRequest(httpMethod=PUT, protocol=http, host=localhost, port=42741, encodedPath=/bucket/key, headers=[amz-sdk-invocation-id, Content-encoding, Content-Length, Content-Type, Expect, User-Agent, x-amz-content-sha256, x-amz-decoded-content-length, x-amz-sdk-checksum-algorithm, x-amz-trailer], queryParameters=[partNumber, uploadId])"

We can filter out this "Retrying Request" log from the stream so that only the progression bar logs appear.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[RanVaknin]

Integ tests are passing

[L-Applin]

Do we know why the request was retrying in the first place?

[RanVaknin]

The test in question tests the TransferListenerContext directly, and not uses the underlying transfer manager/ s3 client. Therefore I don’t think the log for the “Retrying Request” we are seeing is actually from this test.
The logger might get a shared scope somehow (maybe here?) and the error messages are getting polluted from other s3 tests that are running concurrently.

[joviegas]

I think we donot require this fix after #5948