Hide shopping cart menu only if request is coming from a micro site and
requested page is from courseware.

Shopping Cart menu should not be visible in case of while label site.

added tests

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

TNL-2497

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

Added columns to the CC purchases report. (added Qty and Total Discount. Moved the Total Amount to the last index).
Coupon code report.

Removed the unused try/except block around filter().

MAYN-65 fixed the bug, removed the redemption table entry when the item is expired from the user cart

fix quality issues

XCOM-213 XCOM-214

ECOM-653

Update edx-lint to the version that checks if tearDown uses super.

Convert a number of tearDown methods into addCleanup.

Remove some unneeded tearDown methods: no need to call patch.stopall if
none of them were started with patch.start.

The new "country access" implementation replaces the old
implementation.  Middleware and tests have been updated
accordingly, but deprecated models are preserved
for backwards compatibility.

Block users from enrolling in a course if the user
is blocked by country access rules.

1) Enrollment via the login/registration page.
2) Enrollment from the marketing iframe (via student.views.change_enrollment)
3) Enrollment using 100% redeem codes.
4) Enrollment via upgrade.

This does NOT cover enrollment through third party authentication,
which is sufficiently complex to deserve its own commit.

Show ordinary receipt unless the student is in the payment flow.

Remove submission of verification attempt in shopping cart, since it's no longer needed with the new payment/verification flow.

Wrap send email operation in try/except to avoid rolling back the transaction once a user has paid.

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]

Conflicts:
	lms/djangoapps/shoppingcart/views.py

ECOM-891: Allow tracking of invoice transactions.

Authors: Awais Qureshi and Aamir Khan