Resolve boto3/botocore upgrade e2e test failure

[joelvdavies]

See #141. I had to downgrade the updated version of boto3/botocore in this PR in order to get the e2e tests to pass. We should figure out why this is the case and if possible fix it so we can update these too.

[joelvdavies]

As mentioned on the PR, it appears its caused due to
* api-change:``s3``: [``botocore``] This change enhances integrity protections for new SDK requests to S3. S3 SDKs now support the CRC64NVME checksum algorithm, full object checksums for multipart S3 objects, and new default integrity protections for S3 requests.

When testing the versions used in the docker container is irrelevant, only the local version used to run the e2e tests causes it.

Testing locally I now believe that the updated version adds checks on the response header from the object storage and raises this error if not found in the response. Upgrading minio to RELEASE.2025-04-08T15-41-24Z fixed it, so in order to upgrade we both need to update minio from the outdated version of RELEASE.2024-09-13T20-26-02Z (here and on docker-ims), as well as retest this updated package with the a bucket on echo to ensure it wont be an issue for production as well. Ideally this should be done before release so we can have the updated version for production if possible.

[joelvdavies]

I just created a bucket on echo, verifying the tests failed locally but worked when setting using the bucket so I believe this is a minio specific issue in this case that can be resolved by upgrading it. I also tested the echo version manually myself and again it seemed to work fine.

[joelvdavies]

While trying to test the new prod config for docker-ims I discovered I could not upload images due to the same missing content error while using echo, so must have missed something/didn't actually have the updated package installed in the docker container at the time of testing. As a result this will need to be reverted and addressed later once echo is upgraded.