chore: Upgrade Python requirements

[edx-requirements-bot]

Python requirements update. Please review the changelogs for the upgraded packages.

Deleted obsolete pull_requests:
#530

[edx-requirements-bot]

List of packages in the PR without any issue.

• astroid changes from 3.3.6 to 3.3.8
• boto3 changes from 1.35.82 to 1.36.17
• botocore changes from 1.35.82 to 1.36.17
• cachetools changes from 5.5.0 to 5.5.1
• charset-normalizer changes from 3.4.0 to 3.4.1
• click changes from 8.1.7 to 8.1.8
• code-annotations changes from 2.1.0 to 2.2.0
• coverage[toml] changes from 7.6.9 to 7.6.12
• django changes from 4.2.17 to 4.2.19
• edx-lint changes from 5.4.1 to 5.6.0
• filelock changes from 3.16.1 to 3.17.0
• importlib-metadata changes from 8.5.0 to 8.6.1
• jinja2 changes from 3.1.4 to 3.1.5
• keyring changes from 25.5.0 to 25.6.0
• lxml changes from 5.3.0 to 5.3.1
• lxml[html-clean] changes from 5.3.0 to 5.3.1
• mako changes from 1.3.8 to 1.3.9
• more-itertools changes from 10.5.0 to 10.6.0
• newrelic changes from 10.4.0 to 10.6.0
• openedx-filters changes from 1.12.0 to 1.13.0
• pbr changes from 6.1.0 to 6.1.1
• psutil changes from 6.1.0 to 6.1.1
• pygments changes from 2.18.0 to 2.19.1
• pyjwt changes from 2.6.0 to 2.10.1
• pylint changes from 3.3.2 to 3.3.4
• pymongo changes from 4.10.1 to 4.11.1
• pyproject-api changes from 1.8.0 to 1.9.0
• s3transfer changes from 0.10.4 to 0.11.2
• setuptools changes from 75.6.0 to 75.8.0
• tox changes from 4.23.2 to 4.24.1
• twine changes from 6.0.1 to 6.1.0
• virtualenv changes from 20.28.0 to 20.29.2
• xblock changes from 5.1.0 to 5.1.2

[edx-requirements-bot]

These Packages need manual review..

• [MAJOR] attrs changes from 24.3.0 to 25.1.0
• [MAJOR] certifi changes from 2024.12.14 to 2025.1.31
• [NEW] id (1.5.0) added to the requirements
• [MAJOR] isort changes from 5.13.2 to 6.0.0
• [REMOVED] pkginfo (1.12.0) removed from the requirements
• [MAJOR] pytz changes from 2024.2 to 2025.1

[feanil]

@Faraz32123 can you dig into these failures and see if we can land the requirements update here?

[Faraz32123]

@Faraz32123 can you dig into these failures and see if we can land the requirements update here?

Sure, @feanil I'll look into these...

[Faraz32123]

Hey @feanil,
closing this PR in favor of this #535. Feel free to re-open this PR if needed.
I had to create a new PR instead of directly committing to this branch as I didn't had the write access to this repo.