Fall-back to the old path.

Once the LMS has fully switched over to this new path [1],
we can remove the legacy (LMS) import support here.

- [1] https://github.com/edx/edx-platform/pull/27289

* Improve content presentation and add multiple content display support

This commit:
* Improves LTI content presentation handling, and correctly displays LTI DL content in the LMS
* Adds support for presenting multiple DL content items on the same block

* Addressing review comments

* Nits

* Improve test and fix issue

[BD-24][TNL-8072]

* Python code cleanup by the cleanup-python-code Jenkins job.

This pull request was generated by the cleanup-python-code Jenkins job, which ran
```
add_common_constraint; make upgrade
```

The following packages were installed:
`edx-repo-tools`

* Added --django-settings-module to pylint

* Changed position

* Remove django-settings-module from pylint command

* Add django-not-configured in pylintrc

Co-authored-by: Muhammad Soban Javed <58461728+iamsobanjaved@users.noreply.github.com>

[BD-24][TNL-7919] LTI Advantage Names and Roles provisioning service implementation direction (#142)

* Add wip ADR about NRPS

* Nit

* Update docs/decisions/0004-lti-advantage-nrps.rst

Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>

* Update docs/decisions/0004-lti-advantage-nrps.rst

Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>

* Address nits

* Write a bit more

* Update docs/decisions/0004-lti-advantage-nrps.rst

Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>

* Update docs/decisions/0004-lti-advantage-nrps.rst

Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>

* Update docs/decisions/0004-lti-advantage-nrps.rst

Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>

* Update docs/decisions/0004-lti-advantage-nrps.rst

Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>

* Update docs/decisions/0004-lti-advantage-nrps.rst

Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>

* Nits

Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>

* Improve logging and error message presentation

* Add full deep linking content data on studio

* Internationalize LTI 1.3 templates

* Add translation tooling

Signed-off-by: Giovanni Cimolin da Silva <giovannicimolin@gmail.com>

* Update translations

* Address review comments

* Additional logging improvements

* Address review comments, fix test

Signed-off-by: Giovanni Cimolin da Silva <giovannicimolin@gmail.com>

* Commits:
  chore: Bump version to 2.7.1
  fix: Manually backfill lti_config dicts

The difficulty here is that the empty string in an invalid JSON
dictionary (as opposed to None/NULL or '{}' which is just "blank");
attempts to instantiate models would fail, given the invalid data. This
meant we couldn't use the Django ORM to handle the migration entirely;
we need to craft some raw SQL to work-around these checks and
limitations.

Related-To: 42a9e342
Related-To: https://github.com/edx/xblock-lti-consumer/pull/144

* Commits:
  fix: Manually backfill config_id UUIDs again

The previous backfills handled NULL entries;
this handles empty strings.

The difficulty here was that since the empty string in an invalid UUID
(as opposed to None/NULL which is just "blank"), attempts to instantiate
models would fail, given the invalid data. This meant we couldn't use
the Django ORM to handle the migration entirely; we need to craft some
raw SQL to work-around these checks and limitations.

* Implement ltiResourceLink content presentation

Signed-off-by: Giovanni Cimolin da Silva <giovannicimolin@gmail.com>

* Add tests

* Fix serializer required fields issue

Signed-off-by: Giovanni Cimolin da Silva <giovannicimolin@gmail.com>

* Update version and changelog

fix: Migrate the UUID backfill again

Add test for image

Fix broken tests

Add `html` content type serializer

Fix broken tests

Add serializer for `link` content type

[TNL-7520] - Handle case when modal height and width and set to empty in LTI component in studio.

To correct the, in our case, single database entry that snuck in without
a UUID during the schema change.

Steps:
- Make the field editable
- Add `config_id` to all models missing it
- Make the field noneditable again

This implements the endpoint that LTI tools use to return the deep linking configuration to the LMS, along with the `ltiResourceLink` type to allow testing with demo tool.

Signed-off-by: Giovanni Cimolin da Silva <giovannicimolin@gmail.com>

Signed-off-by: Giovanni Cimolin da Silva <giovannicimolin@gmail.com>

Python Code Cleanup

* Commits:
  Fix migration `config_id` conflict.

A previous PR (#130) added a new unique field with a default value to the
LtiConfiguration model. Such cases need special handling in migraiton, however
the previous PR did not include that. This commit fixes the migration to include
the special handling for new unique fields.

Remove the OIDC view from XBlock and return OIDC url directly.

[BD-03] [TNL-7742] [BB-3370] Add LTI 1.1 config on model

* Commits:
  Skip migration when no LTI XBlock location exists

otherwise this blows up, trying to migrate a record with no location
(the modulestore lookup throws).

Presumably this isn't (wasn't?) an issue in prod already, right?
But I did hit this in my devstack, having previously created an
LtiConfiguration record via Django Admin (without a location).

* bump up the version

* update changelog