feat: Update the user_authn app to not log PII by default.

updated for quality

[TSD] Annotate git export settings and toggles in CMS

* Commits:
  fix: Add DiscussionsConfiguration.enabled to admin page

* Commits:
  style: Cleanup DiscussionsConfiguration.__str__

Instead of optionally not logging usernames and emails, do so by
default.  This mostly removes some complexity from the app and is makes
it so that it's more secure by default.

I considered the question of allowing people to log usernames and
e-mails if they wanted to but opted not to for a couple of reasons:

* It would involve adding a new feature flag that would be the opposite
of the SQUELCH_PII_IN_LOGS which would be a bit confusing.  When do you
use which one? or do you need both? etc.
* There is still a way to correlate the messages to eachother and in
most cases also to a specific user(email being the exception).

Lower the pylint threshold to 200

The size of commons.js has gradually grown until it is now 4 MB in
dev mode. This change brings it back down to 880 KB. This does
cause the size of some other JS assets to increase, some by as much
as 500 KB. This still seemed like a worthwhile tradeoff.

Added to serve old login/register pages for the e2e tests
until new tests added or old ones are fixed for the Authn MFE.

Remove duplicate constraints

Python Requirements Update

BOM-2345: Applied pylint-amnesty

Now that we always return an existing value from the DB rather than trusting that ID generation is deterministic and constant over time, we're free to change the generation algorithm.

Our long term goal is to switch to random IDs, but we need to first investigate the uses of save=False. In the meantime, this is a good opportunity to move away from MD5, which has a number of cryptographic weaknesses. None of the known vulnerabilities are considered exploitable in this location, given the limited ability to control the input to the hash, but we should generally be moving away from it everywhere for consistency.

This change should not be breaking even for save=False callers, since those calls are extremely rare (1 in 100,000) and should only occur after a save=True call, at which point they'll use the stored value. Even if this were not true, for a save=False/True pair of calls to result in a mismatch in output, the first of the calls would have to occur around the time of the deploy of this code.

Co-authored-by: Tim McCormack <tmccormack@edx.org>
 
Co-authored-by: Tim McCormack <tmccormack@edx.org>

* 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

We take the opportunity to resolve a few linting issues, without affecting the
feature behaviour.

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