Upgrade boto to boto3

Description

*What changed?*

Boto is the old library that was used to interact with the AWS APIs, and
in particular the S3 API. It was replaced by boto3. We need to upgrade
boto to boto3 because boto makes it near impossible to customize the
connection settings.

It goes without saying that this should be tested with edX.org's own S3 settings to check whether the new configuration is compatible. In particular, it is possible that the default calling format has changed from "subdomain" to "ordinary".

*Developer Checklist*

  • [x] Reviewed the [release process](./release_process.md)

  • [x] Translations up to date

  • [ ] ~JS minified, SASS compiled~

  • [ ] Test suites passing on Jenkins

  • [x] Bumped version number in [setup.py](../setup.py) and [package.json](../package.json)

FIY: @edx/masters-devs-gta

Assignee

Unassigned

Reporter

Open Source Pull Request Bot

Labels

Contributor Name

Régis Behmo

Repo

edx/edx-ora2

Customer

None

Epic Link

None

OSCM Assignee

None

Platform Map Area (Levels 1 & 2)

Developer Experiences - Pattern Library & Components

Platform Map Area (Levels 3 & 4)

None

Blended Hour Utilization Percentage

None

Priority

Unset
Configure