boto3 >=1.36.0 breaks most non-AWS S3 providers

[calwe24]

Package version (if known): N/A

Describe the bug

boto3 recently updated to enforce checksum validation on all requests by default - including S3. This broke many S3 providers as they don't support this: boto/boto3#4392

Any operation that interacts with the S3 bucket will now fail, such as attempting to upload a file. The browser recieves an HTML 500 error, and the Invenio logs will complain about 'MissingContentLength'. It can be fixed by either downgrading boto3, or setting the env variables AWS_REQUEST_CHECKSUM_CALCULATION and AWS_RESPONSE_CHECKSUM_VALIDATION to WHEN_REQUIRED. It was discussed in the Invenio discord server that these should be added as option that can be set in invenio.cfg, rather than as env variables.

Expected behavior

Screenshots (if applicable)

Additional context

[tmorrell]

I think the env variables are the way to go (versus pinning), since folks with a non-AWS S3 provider will know they already have to do some configuration. I think we should add these config options to the docs here https://inveniordm.docs.cern.ch/customize/s3/#amazon-s3, in a new section below Amazon S3.