* feat: support assessment control claims

* test: unit tests

* feat: ACS scope handling

* fix: correct acs url

* fix: removed drafted signal code

* test: added permissions test

* docs: added note on individual file testing

* docs: moved unit testing notes to readme

* chore: version bump

* temp: broken code to filter ACS scope perms

- Tried to create a filter in the access_token end point to only add the ACS scope only when proctoring is enabled
- This seems to hard to do without causing a circular dependency

* fix: removed filter for ACS access token

---------

Co-authored-by: Zach Hancock <zhancock@edx.org>

* feat: support assessment control claims

* test: unit tests

* docs: docstring update

* feat: only enable ACS on start message

build: bump library version and add CHANGELOG entry

I neglected to bump the library version and update the CHANGELOG for the changes made in #363. This commit corrects that.

feat: add full name as a LTI PII field

Python Requirements Update

This commits adds the ability to share a learner's full name in both LTI 1.1 and LTI 1.3 launches. In LTI 1.1, the full name is sent as the "lis_person_name_full" LTI parameter. In LTI 1.3, the full name is sent as the "name" ID token claim.

The full name corresponds to the learner's name as recorded by the UserProfile model in the LMS.

Enabling the transmission of full name in either version of LTI follows the existing pattern for PII sharing. In order for full name to be shared via an LTI launch, the CourseAllowPIISharingInLTIFlag configuration model must be enabled for the course, and the "Request user's full name" XBlock field must be enabled in the XBlock describing the particular LTI integration.

Please note that this commit does not add the ability to share a learner's full name via the LTI 1.3 Names and Role Provisioning Services context membership endpoint because that behavior already exists.

* Adds support for compiling, loading, and translating JavaScript translations

feat: standardize translation directory for i18n_tool

feat: add logging for access token view and key handlers

This commit adds logging for error cases in the access_token_endpoint view and the key handler classes. This will make it easier to debug issues with requesting or using LTI 1.3 access tokens.

Co-authored-by: Varsha <46579265+varshamenon4@users.noreply.github.com>

Refs: FC-0012 OEP-58

* feat: translation safe pii dialogue

* feat: extract translations

* Adds lti_1p3_redirect_uris to XBlock
* Adds lti_1p3_redirect_uris to LTIConfiguration model
* Asserts redirect_uri from preflight response in valid redirect uris during preflight validation
* To minimize disruption for previous versions, uses current launch url and deep linking url as default registered redirect_uris if redirect_uris is not explicitly set

Update standard workflow files.

build: Updating a missing workflow file `add-depr-ticket-to-depr-board.yml`.

The .github/workflows/add-depr-ticket-to-depr-board.yml workflow is missing or needs an update to stay in
sync with the current standard for this workflow as defined in the
`.github` repo of the `openedx` GitHub org.

build: Creating a missing workflow file `add-remove-label-on-comment.yml`.

The .github/workflows/add-remove-label-on-comment.yml workflow is missing or needs an update to stay in
sync with the current standard for this workflow as defined in the
`.github` repo of the `openedx` GitHub org.

build: Creating a missing workflow file `self-assign-issue.yml`.

The .github/workflows/self-assign-issue.yml workflow is missing or needs an update to stay in
sync with the current standard for this workflow as defined in the
`.github` repo of the `openedx` GitHub org.

fix: inappropriate instructions for inline PII sharing consent dialog

This commit fixes inappropriate instructions displayed when collecting PII sharing consent before an inline LTI launch. Previously, the instructions said, "Click OK to have your [username (and) e-mail address] sent to a 3rd party application. Click Cancel to return to this page without sending your information." The latter sentence does not make sense in the context of an inline launch, because there is no cancel button. This commit modifies the inline PII sharing consent dialog to say, "Click OK to have your [username (and) e-mail address] sent to a 3rd party application.""

feanil/django pyfs

feanil/make upgrade

The code in this repo has been updated to work with bleach 6.0.0 and
will break with older versions so make that dependency clear in base.in
and do a major version update.

We don't use it directly here and it's an implicit dependency of
xblock-sdk so we don't need to have it listed explicitly in test.in

The code in this repo has been updated to work with bleach 6.0.0 and
will break with older versions so make that dependency clear in base.in
and do a major version update.