Remove the "role of users being enrolled" field from Instructor Dashboard

Added BearerAuthenticationAllowInactiveUser in courseware view

MICROBA-1024 | Move checks to certificates app

add user id (staff only) field in user_api

LEARNER-8158 
Fixed descendants typo and added tests

* refactor: use q objects when fetching user using an identifier #26683

* Nit

* The original use of user.has_perm('can_take_proctored_exam') in the get_active_enrollments_for_course method had very poor performance when used for multiple learners. The permission is not designed for use in bulk operations. It was being called for each user in a loop by edx-proctoring, resulting in many queries to the database. This lead to timeouts on the client. This change exposes a new service endpoint that performs this permission checking in the database, resulting in one single query to the necessary LMS SQL tables and many fewer queries to the modulestore.

* bump version of edx-proctoring to 3.7.3

feat: add 'external course updates' experiment flag

[MICROBA-1024]
- Move some of the recently added logic from the instructor app to the certificates app
- Attempt to not use other certificate models directly in the code I am touching, moving this logic to certificates as well.

When this flag is enabled, users will be 50/50 bucketed into an
experiment where users get course highlights and nudges from an
external service (like sailthru or braze) rather than from
edx-platform via ACE.

AA-661

AA-510: a11y fix for learner dashboard enterprise link

Add hover for accordion

update edx-proctoring version

The Django setting
FEATURES['ENABLE_COURSEWARE_MICROFRONTEND']
has been an additional gate to activating
usage of the Learning MFE for an Open edX
instance.

The toggle is redundant with the
`courseware.courseware_mfe`
Waffle flag. By removing it, we simplify our config
and simplify our path towards making the Learning MFE
the default courseware experience.

TNL-7796

[MST-666] Update edx-proctoring to 3.7.0

fix: Text comparison should be done with `==` not via is.

doc: Correctly annotate the setting name.

AA-513: Ensure user id exists before trying to send event

request.user.id could be None which ends up raising an error in
the analytics package we use.

Run Pyupgrade on entitlement.

Run Pyupgrade on student folder. 

BOM-2351: Removed unused imports from common/lib/{capa, safe_lxml, sy…

The `setting_name` annotation needed a space before it so that it's
picked up properly by the toggle annotations tooling.

`is` will check if two objects are the same whereas `==` will check if
their values are the same which is what we want here.

Check course outline and course date toggles in addition to courseware toggle for streak

AA-682: Update the pseudo session fallback session

There was a bug where the earliest course returned for a pseudo session
(when there were no available sessions) might not exist in modulestore and
would cause a 500 error. The data problem is another issue that will need to
be fixed, but by switching to the most recent session in this scenario, we believe
we will reduce the likelihood of this error occurring. We also believe the most
recent session is a better return value than the first ever session.