Increase default MAX_PAYLOAD_BYTES_TO_PRINT to 100MiB

[AndreKurait]

Description

Increases MAX_PAYLOAD_BYTES_TO_PRINT to 100 MiB to keep in line with AWS Opensearch Support

• Category: Bug Fix
• Why these changes are required? The default configuration should work with aws opensearch
• What is the old behavior before changes and new behavior after changes? Large requests over 1MB would not be included in the tuple output. Now by default all requests that are supported within AWS Managed Opensearch will work.

Issues Resolved

MIGRATIONS-1715

Is this a backport? If so, please add backport PR # and/or commits #

Testing

Unit Testing

Check List

• [x ] New functionality includes testing
  • [ x] All tests pass, including unit test, integration test and doctest
• [x ] New functionality has been documented
• [x ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[gregschohn]

This is sloppy, but I'm fine doing this since we're already tracking the bytes anyway. I'm also OK since we'll likely soon be discarding this code to stream it w/out the aggregator anyway.