Co-authored-by: Simon Chen <schen@edX-C02FW0GUML85.local>

chore: update lti-consumer-xblock version to 3.1.1

the latest version contains an update that reduces the amount of celery tasks
triggered by name affirmation updates

ENT-5095

* fix: pin docutils<0.18 due to Sphinx requirement

fix: use pngs for the goal reminder email banner and remove redundant unsubscribe link from the email (#29215)

* fix: use pngs for the goal reminder email banner and remove redundant unsubscribe link

* fix: update

ENT-5115

[3.33.5]
---------
fix: CSOD API session tokens are now saved to the customer's configuration instead of individual transmission audits

[3.33.4]
---------
feat: integrated channels only requests content metadata for courses that need updating

[3.33.3]
---------
feat: Change Bulk Enrollment Assignment Logic for Pending learners

[3.33.2]
---------
fix: no longer notify learners of already existing enrollments

ENT-5115

analytics API use is in separate repositories, mostly analytics
dashboard

* feat: degreed2 integrated channels

ENT-2789

* feat:  New integrated channel via edx-enterprise

* fix: pull in edx-enterprise 3.33.1

fixes db_overrides check failure by renaming field `key` to `client_id`

The VERIFIED_NAME_FLAG, the VerifiedNameEnabledView, and the verified_name_enabled key removed from responses for both VerifiedNameView view and VerifiedNameHistoryView
were removed as part https://github.com/edx/edx-name-affirmation/pull/12. This was released in version 2.0.0 of the edx-name-affirmation PyPI package. Please see below for additional context for the removal, copied from the name-affirmation commit message.

The VERIFIED_NAME_FLAG was added as part https://github.com/edx/edx-name-affirmation/pull/12, [MST-801](https://openedx.atlassian.net/browse/MST-801) in order to control the release of the Verified Name project. It was used for a phased roll out by percentage of users.

The release reached a percentage of 50% before it was observed that, due to the way percentage roll out works in django-waffle, the code to create or update VerifiedName records was not working properly. The code was written such that any change to a SoftwareSecurePhotoVerification model instance sent a signal, which was received and handled by the Name Affirmation application. If the VERIFIED_NAME_FLAG was on for the requesting user, a Celery task was launched from the Name Affirmation application to perform the creation of or update to the appropriate VerifiedName model instances based on the verify_student application signal. However, we observed that when SoftwareSecurePhotoVerification records were moved into the "created" or "ready" status, a Celery task in Name Affirmation was created, but when SoftwareSecurePhotoVerification records were moved into the "submitted" status, the corresponding Celery task in Name Affirmation was not created. This caused VerifiedName records to stay in the "pending" state.

The django-waffle waffle flag used by the edx-toggle library implements percentage rollout by setting a cookie in a learner's browser session to assign them to the enabled or disabled group.
It turns out that the code that submits a SoftwareSecurePhotoVerification record, which moves it into the "submitted" state, happens as part of a Celery task in the verify_student application in the edx-platform. Therefore, we believe that because there is no request object in a Celery task, the edx-toggle code is defaulting to the case where there is no request object. In this case, the code checks whether the flag is enabled for everyone when determining whether the flag is enabled. Because of the percentage rollout (i.e. waffle flag not enabled for everyone), the Celery task in Name Affirmation is not created. This behavior was confirmed by logging added as part of https://github.com/edx/edx-name-affirmation/pull/62.

We have determined that we do not need the waffle flag, as we are comfortable that enabling the waffle flag for everyone will fix the issue and are comfortable releasing the feature to all users. For this reason, we are removing references to the flag.

[MST-1130](https://openedx.atlassian.net/browse/MST-1130)

Co-authored-by: Simon Chen <schen@edx-c02fw0guml85.lan>

Co-authored-by: Simon Chen <schen@edx-c02fw0guml85.lan>

This would set the ProctoredExamSoftwareSecureReview.video_url field to be nullable

Co-authored-by: Simon Chen <schen@dhcp-10-31-74-156.dyn.MIT.EDU>

With this new version, the edx-proctoring library is running on Django3.2 instead of Django2.2

Co-authored-by: Simon Chen <schen@dhcp-10-31-74-156.dyn.mit.edu>

Bump ORA to 3.7.4. This version introduces custom window.confirm-esque prompts, because Chrome and Safari have begun to disallow window.confirm from within cross-origin iframes.

To gain further information about why VerifiedName records are not reliably transitioning from "pending" to "submitted", version 1.0.3 adds additional logs to test that the IDV related signals are being received successfully and successfully triggering the Celery task. This code change installs this new version into the platform.

[MST-1130](https://openedx.atlassian.net/browse/MST-1130)

Updates query counts for the additional query to look up the Schedule
in edx-when

with logging fix for blackboard PR 1389 for edx-enterprise

release edx-enterprise 3.30.10
ENT-5043