Fix flaky S3 multipart PUT test

[davidh44]

Motivation and Context

Fix flaky S3 Multipart PUT tests by increasing invocation count caps

Similar to previous fixes #6399 && #6540

com.github.tomakehurst.wiremock.client.VerificationException: 
Expected exactly 1 requests matching the following pattern but received 2:
{
  "method" : "PUT",
  "queryParameters" : {
    "partNumber" : {
      "matches" : "1"
    }
  }
}
    at com.github.tomakehurst.wiremock.client.WireMock.verifyThat(WireMock.java:650)
    at com.github.tomakehurst.wiremock.client.WireMock.verifyThat(WireMock.java:630)
    at com.github.tomakehurst.wiremock.client.WireMock.verify(WireMock.java:671)
    at software.amazon.awssdk.services.s3.internal.multipart.S3MultipartClientPutObjectWiremockTest.mpuDefaultSplitImpl_partsFailOfRetryableError_shouldFail(S3MultipartClientPutObjectWiremockTest.java:201)

com.github.tomakehurst.wiremock.client.VerificationException: 
Expected exactly 2 requests matching the following pattern but received 3:
{
  "method" : "PUT",
  "queryParameters" : {
    "partNumber" : {
      "matches" : "2"
    }
  }
}
    at com.github.tomakehurst.wiremock.client.WireMock.verifyThat(WireMock.java:650)
    at com.github.tomakehurst.wiremock.client.WireMock.verifyThat(WireMock.java:630)
    at com.github.tomakehurst.wiremock.client.WireMock.verify(WireMock.java:671)
    at software.amazon.awssdk.services.s3.internal.multipart.S3MultipartClientPutObjectWiremockTest.mpuWithBufferedSplittableAsyncRequestBody_partsFailOfRetryableError_shouldRetry(S3MultipartClientPutObjectWiremockTest.java:172)

[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]

Can you please just add the failure stack trace to the PR?

[github-actions]

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.