It was introduced back in 2012, and is not used in the default
configuration.

There's no need to use a string literal in setattr, delattr, or the
two-argument form of getattr.

Remove filtering by partition, course and user
Rewrite the LMS result processor to use the course blocks api

These signals are caught by the Teams app and used to update
`last_activity_at` on both teams and individual users.

TNL-2497

TNL-2864

New classes for the return type, and changes to the has_access function and tests to make them compatible.

Skipped 'print' statement violations, as print() is Py3k syntax.

Cannot hold on to xblock references.

The existing pattern of using `override_settings(MODULESTORE=...)` prevented
us from having more than one layer of subclassing in modulestore tests.

In a structure like:

    @override_settings(MODULESTORE=store_a)
    class BaseTestCase(ModuleStoreTestCase):
        def setUp(self):
            # use store

    @override_settings(MODULESTORE=store_b)
    class ChildTestCase(BaseTestCase):
        def setUp(self):
            # use store

In this case, the store actions performed in `BaseTestCase` on behalf of
`ChildTestCase` would still use `store_a`, even though the `ChildTestCase`
had specified to use `store_b`. This is because the `override_settings`
decorator would be the innermost wrapper around the `BaseTestCase.setUp` method,
no matter what `ChildTestCase` does.

To remedy this, we move the call to `override_settings` into the
`ModuleStoreTestCase.setUp` method, and use a cleanup to remove the override.
Subclasses can just defined the `MODULESTORE` class attribute to specify which
modulestore to use _for the entire `setUp` chain_.

[PLAT-419]

TNL-652

TNL-651

Co-Authored-By: Christina Roberts <christina@edx.org>
Co-Authored-By: Daniel Friedman <dfriedman@edx.org>
Co-Authored-By: Don Mitchell <dmitchell@edx.org>

TNL-1022

Move lms.lib.xblock into lms.djangoapps.lms_xblock in preparation add database backed configuration to it

TNL-670

TNL-649