* Updating Python Requirements

* change namespaced_switch_name to name

Co-authored-by: Zulqarnain <muhammad.zulqarnain@arbisoft.com>

field added in validate decisions for authn

Make rate limit errors 429s instead of 403s

VAN-351

replace bulk transmission task to intended single learner task

bumping enterprise to 3.17.25

MICROBA-918 Check the allowlist when regenerating certificates, and stop incidentally modifying the certificate invalidation list (#26439)

AA-590: pass translated tab titles to MFE

Updated Pylint Warnings

Mergeback PR from private to public.

Added BearerAuthenticationAllowInactiveUsern in celebration api

Update Thresholds

Merge pull request #219 from edx/matthugs/EDUCATOR-5555-a11y-js-code-for-notes-needs-to-handle-tags-better

Fix XSS vector for a11y text attached to notes editor

Lower down pylint error thresholds

Make credentials celery tasks errors consistent

bumping enterprise to 3.17.24

This deprecates `save=False` for several functions and removes all known
usages of the parameter but does not actually remove the parameter.
Instead, it will emit a deprecation warning if the parameter is used.
We can remove the parameter as soon as we feel sure nothing is using it.

Now that we have refactored `anonymous_id_for_user` to always prefer
retrieving an existing ID from the database -- and observed that only a
small fraction of calls pass save=False -- we can stop respecting
save=False. This opens the door for future improvements, such as generating
random IDs or switching to the external user ID system.

Metrics: I observe that 1 in 16 requests for new, non-request-cached
anon user IDs are made with save=False. But 71% of all calls are served
from the request cache, and 99.7% of the misses are served from the DB.
save=False only appear to come from intermittent spikes as reports are
generated and are low in absolute number.

Also document usage/risk/rotation of secret in anonymous user ID
generation as indicated by `docs/decisions/0008-secret-key-usage.rst`
ADR on `SECRET_KEY` usage.

ref: ARCHBOM-1683

Currently it's hard to see the content of an error without knowing how
to cause an existing view to make that error in production.  Adding
these default paths should make that a lot easier.

See context here: https://django-ratelimit.readthedocs.io/en/latest/cookbook/429.html#context

For now we continue to fall back to django's default 403 handler for 403
but provide a new 429 template that we use for ratelimit exceptions.

This commit also updates a logistration test that relied on the old 403
behavior of django-ratelimit instead of the newly added 429 behavior.

In order to better alert off of tasks that failed after maximum retries,
this makes the the error for each task consistent with itself.

[MST-645] Account for no enrollment in courseware rules

AA-650: block deprecated keys from course home MFE

Update to newest edx-lint

Copy existing pylintrc changes to pylintrc_tweaks

Feanil/rate limit anon csv

Update Library v2 Indexes to work with ElasticSearch 7. Repair blockstore integration tests. (#26230)