Migrate python-kms to 2.0.0

[ozer550]

Summary

This Pr intends to make the required changes to upgrade the python-kms library to its newest major release 2.0.0.
fixes #3885

Description of the change(s) you made

• Migrated and made changes according to this guide.
• Added some changes that were not mentioned in the guide like this.
• Added crc32c checksum mechanism according to standards and snippets given here.

Are there any risky areas that deserve extra testing?

There maybe some changes that I have missed, but I tried my best to catch most of them! If there are some changes missed I will be happy to debug them and make the required changes.

Comments

Additionally added the crcmod package for checksum mechanism as described here.

Contributor's Checklist

PR process:

• If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
• If this includes an internal dependency change, a link to the diff is provided
• The docs label has been added if this introduces a change that needs to be updated in the user docs?
• If any Python requirements have changed, the updated requirements.txt files also included in this PR
• Opportunities for using Google Analytics here are noted
• Migrations are safe for a large db

Studio-specifc:

• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
• All UI components are LTR and RTL compliant
• Views are organized into pages, components, and layouts directories as described in the docs
• Users' storage used is recalculated properly on any changes to main tree files
• If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

• Code is clean and well-commented
• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Any new interactions have been added to the QA Sheet
• Critical and brittle code paths are covered by unit tests

---

Reviewer's Checklist

This section is for reviewers to fill out.

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[bjester]

Could you use zlib for the crc32 checksum instead of adding a new dependency? Like this

studio/contentcuration/contentcuration/utils/celery/tasks.py

Line 162 in 6dfeae9

key2 = zlib.crc32(signature.encode('utf-8'))

[bjester]

Could you use zlib for the crc32 checksum instead of adding a new dependency? Like this

studio/contentcuration/contentcuration/utils/celery/tasks.py

Line 162 in 6dfeae9

key2 = zlib.crc32(signature.encode('utf-8'))

Ah this is crc32c not crc32, which I guess isn't builtin with zlib

[bjester]

One dependency change by me, but approving so we can test it in CD

[bjester]

CD completed successfully and the unstable server is still functioning appropriately.