Configure s3 in the containerized environment for file upload e2e tests

[GPortas]

What this PR does / why we need it:

Adds S3 remote storage option using a bucket hosted on AWS.

Initially, I evaluated using localstack as in js-dataverse to avoid using AWS and to keep everything containerized. After encountering issues and limitations, I decided to use a remote S3 storage.

Which issue(s) this PR closes:

• Closes Configure localstack s3 in the containerized environment for file upload e2e tests #456

Special notes for your reviewer:

Now we need to create a .env under dev-env folder, by copying the .env.example file, and paste there the credentials for AWS. I will be happy to share them, just ping me on Slack. @ekraffmiller @ErykKul @GermanSaracca

The AWS secrets are already added to the repository for the GitHub actions to operate.

Suggestions on how to test this:

Run docker containers locally and create a dataset. Next, verify that direct upload works on JSF.

[coveralls]

coverage: 97.733% (-0.02%) from 97.754%
when pulling 0ca4a1f on 456-localstack-s3-env
into 5832262 on develop.

[g-saracca]

I followed the steps and was able to successfully create a collection with s3 configured as Storage, and then create a dataset and upload a file to it.

[GPortas]

@GermanSaracca @ErykKul @ekraffmiller

Thanks to Eryk's help, I've managed to set S3 as the default and unique storage option, so there's no need for the intermediate step of creating a dataverse with S3 storage. 🎉

[g-saracca]

@GPortas @ErykKul Works great, S3 is now the default Storage. I was able to create datasets and upload files into them.