Because the courseware microfrontend loads units inside iframes,
the LTI modal ends up being squished and generally ugly.
This PR introduces a new message sent to the parent window to request
a modal containing the contents of the LTI launch iframe.

https://openedx.atlassian.net/browse/TNL-7410

This is just to keep it in line with other xblocks that define
an is_past_due attribute. Nicer if they all have the same access
pattern.

k# Please enter the commit message for your changes. Lines starting

Also fixes a few untreated exceptions and remove unused variables.

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

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

This commit adds support for the LTI 1.3 Access token endpoint, as detailed in the IMS Security Framework.
The token is generated using the consumer's private key (stored in the XBlock) after validating the message sent by the LTI Tool using it's public key.

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

Features:
Implement LTI 1.3 launch support.
Add LTI 1.3 passthrough views as LMS plugins.

This shows the 'problem' icon for LTI units, rather than the default
'other' icon.

AA-75

removed web_fragment deprication warnig

fixed import sequece

updated bleach

Added img to bleach safe tags

Added img to bleach safe tags

Added img to bleach safe tags

added test

added test

added test

added test

added test for attr image

added test for attr image

fixed style bug

Updated format xoe

removed extra formatting

Updated to run tests on both python 2 and 3.

PROD-774

Overview
---------
This pull request makes this XBlock extensible for
adding parameters to the LTI provider in addition
to the existing ones.

Why
---
A customer needs `team` and `cohort` informaiton
to be passed through the LTI channel to simplify
integration with their LTI provider. At the same
time we'd rather not fork the XBlock, so an
Open-Closed model is needed.

More Detailed Documentation
---------------------------
I've added a couple of sections to `README.rst`
to document specifying design and
configuration steps of the new LTI parameter
processors. Please check it out for more
information about the changes that this pull
request introduces.

Example Usage
-------------
I've written a package that we'll need to use for
our customer to pass some personal user
information in addition to the cohort and team
info: https://github.com/appsembler/tahoe-lti/pull/1

Omar Al-Ithawi @ Appsembler

Add context_label and context_title to LTI POST parameters; Add required requirements; add some docker devstack instructions;

The module used for rebind was set to LtiConsumer instead of the xblock,
which is wrong and causing an silent exception thrown and return 404 to
the client without any indication of the cause.

removed ugettext around display name also

updated readme

fixed link

better fix for link