* refactor: reformat the manual verifications command to allow for single user verifications

* reformat error message

* linting

* linting: add doc string

* whitespace

ENT-4361 | Added user's "id" and "email" as public fields in ACCOUNT_VISIBILITY_CONFIGURATION.

feat: stop removing `verify_uuid` value when revoking course certs

Co-authored-by: SaadYousaf <saadyousaf@A006-00314.local>

This reverts commit 35b27806.

During the Lilac stabilization period, try to prod developers to think
about whether they should also update Lilac.

Merge pull request #26860 from open-craft/giantas/bb-3825-fix-new-post-indicator-in-discussion-xblock

[BB-3825] Fix:  Hide new post indicator on thread open

[MB-1077]
- Stop removing the verify_uuid when revoking course certificates. In v2 of course certificates this will allow us to retain the same URL to the certificate. If a learner's certificate is revoked (from being invalidated or no longer passing the course) the UUID will remain intact and the URL will not change.
- Look for an existing cert for the user in a course-run during generation. If one exists, use the UUID from the existing certificate when updating the record.
- Stop generating a `key` for v2 web-certificates. This is not needed for web-certs (this is used in PDF cert generation).

This fixes the removal of the new post indicator in the Discussion XBlock once a thread has been opened.

Allow reset password from Support Tools

* Updated api/user/v1/accounts list view to search based on multiple emails as well.

fix:  Fixes integrated_channels bug in learner_data transmission during course details fetch (#27303)

courseOverview model was being incorrectly used in the learner_data module of integrated_channels

ENT-4222, ENT-4428

[MICROBA-951]

When running the notify_credentials command locally there is an
OperationalError thrown by MySQL when there are no more results
available for the queryset iterator. This change catches that exception,
checks state, and then logs according to that state. This code runs in
production without issue. This changes allows for the code to be run
locally without a separate code path.

This package is no longer used.

Attempting to import packages from
lms/djangoapps, cms/djangoapps, or common/djangoapps
as if they are import roots will now
simply raise ImportErrors (like any other invalid
import) instead of DeprecatedEdxPlatformImportError.

See docs/decisions/0007-sys-path-modification-removal.rst
for more details.

* Use config settings for olxcleaner

Use config settings instead of hardcoded values for olx validation. This would help in adding a great deal of control when you want to change these settings in the future. With this approch we would not need a redeploy.

* Use configs and deprecate waffleflag and also add / update tests

BOM_2408: Removed unused imports from openedx/core/djangoapps/user_api

BOM-2408: Removed unused imports from openedx/core/{djangolib, lib} a…

Add independent ratelimit setting for forms

chore: Remove decentralized devstack config.

chore: update edx-enterprise

We have decided not to pursue the decentralized devstack design right
now and so we want to cleanup files and task that were built as a part
of the process.

Related Ticket: ARCHBOM-1685

* Commits:
  fix: Stop using view_auth_classes helper in discussions API

as it conflicts with the manually-assigned `permission_classes`;
the decorator erases them.

Currently, login and registration forms and view to log the user in
are sharing same ratelimit settings which is causing too much noise
while rendering forms.This PR will introduce a separate
setting for logistration forms.

VAN-436

[MST-738] Pass username into CourseHomeMetadataView

BOM-2408: Removed unused imports from openedx/core/djangoapps/{themin…

BOM-2416: Removed unused imports from docs, scripts, pavelib

feat: add letter grade to MFE Progress Tab API

MICROBA-1106

Removed unused imports from docs, scripts, pavelib

[TNL-8051] - bump olxcleaner version with latest update.

BOM-2350: Removed unused imports from cms using 'unimport'

This adds a new django app to allow the GDPR user retirement via
Open edX's REST API. Prior to this the only way to trigger the user
retirement was either by the user themself clicking "Delete my account"
in the account setting page or via creating a User Retirement request
by admin. With these changes, the user retirement process can be
triggered using REST API.