This commit fixes three bugs.

1. The first bug is that the lti_version field is inappropriately hidden in the Studio author view edit menu when the selected config_type is database.

2. The second bug is that the editable_fields property of the LtiConsumerXBlock is inappropriately excluding LTI 1.3 fields when the config_type is database. The editable_fields property should include LTI 1.3 fields even when the config_type is database, because the Javascript defined in xblock_studio_view.js may want to show these fields if the user selects a different config_type in the menu. We want to support a dynamic edit menu, so these fields must be considered editable by the XBlock in order for the Javascript to be able to manipulate them.

3. The third bug is in inconsistent rendering of the Studio author view edit menu. Depending on the order in which a user selects lti_version, config_type, or lti_1p3_tool_key_mode, different sets of fields are displayed, due to the overlapping sets of rules that govern what fields should be hidden or shown for a given field selection. This commit corrects this inconsistent rendering by first showing all fields and then gradually hiding fields depending on the sets of rules, for each change to the fields.

This commit adds additional core LTI 1.3 and LTI Advantage variables to the LTIConfiguration model. The additional core LTI 1.3 variables are lti_1p3_oidc_url, lti_1p3_launch_url, lti_1p3_tool_public_key, and lti_1p3_tool_keyset_url. The additional LTI Advantage variables are lti_advantage_enable_nrps, lti_advantage_deep_linking_enabled, lti_advantage_deep_linking_launch_url, and lti_advantage_ags_mode.

This commit also adds a configuration type to the LtiConsumerXBlock to support the storage of these LTI variables on the LTIConfiguration model (i.e. the database) instead of the xBlock itself.

Changes that allow the use of this configuration option are behind the lti_consumer.enable_database_config CourseWaffleFlag.

Modified the Lti1p3ApiAuthentication authentication backend to return
AnonymousUser instead of None. This allows DarkLangMiddleware to work
properly without crashing when middleware tries to get a user info
from the request.

This investigation and patch was originally done by @OlhaShyliaieva in:
  https://github.com/openedx/xblock-lti-consumer/pull/228

I'm just rebasing it onto the latest version to land this change.

* feat: add event tracking to lti launch

* style: move tracking fn to new file

* fix: add missed track call to LTI1.3

* feat: release tasks

We are removing this runtime attribute in openedx/edx-platform#30450.

This update caused by removing support for the LegacyWaffle* classes.
See https://github.com/openedx/public-engineering/issues/28 for details.

This adds support for loading LTI 1.1 configurations from external
sources using openedx-filters. It allows the users to select the
configuration provided by the filter and configure the component without
explicitly entering any details.

* Use render_django_template for lti 1p3 launch errs
* Test % trans not found in lti 1p3 err templates
* Bump version to 3.4.6; Update ChangeLog

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

* Fix quote rendering by switching to Django template (from Mako template)
* Internationalize strings on LTI 1.1 launch page

Version 3.3.0 has already been released on PyPi but it was never updated here in that PR and hence there was inconsistency in the version number leading to wrong version bump in the successive PRs. This PR fixes the issue with the version number

feat: add test for consumer xblock with a keyset URL

feat: handle keyset URL failure cases

fix: refactor and clean the tests up

fix: generate translations

fix: version bump

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