Restrict access to users that have not accepted terms of use

[suecarmol]

Description

Describe your changes in detail following the commit message guidelines
Added a condition to check if a user has agreed to the terms of service in order to get any access to the library's collections.

Rationale

The button for an individual partner is not greyed-out when a user has not accepted the terms of service, which shouldn't be happening.

Phabricator Ticket

T260229

How Has This Been Tested?

A test was added to check the correct functionality of the user_update_eligibility management command and made manual tests to check that access is being granted or denied based on acceptance of the terms of use.

Manual test instructions:

Manual test 1:

1. If a user is bundle eligible, has agreed to the terms of use, and is logged in, they should be able to access the collections.
2. Go to the terms of use page and opt-out of the terms.
3. Navigate to the bundle library. Buttons should be greyed-out.
4. Click on one of the bundle partners. The Access Collection button should be greyed-out.
5. Go to the terms of use page and accept the terms again.
6. User should have access to bundle items again

Manual test 2:

1. If a user is bundle eligible, has agreed to the terms of use, and is logged in, they should be able to access the collections.
2. Go to the terms of use page and opt-out of the terms.
3. Log out of your session.
4. Log back in and, without agreeing to the terms of service, navigate to the library bundle page.
5. User should see library bundle permission is expired.
6. Go to the terms of use page and accept the terms again.
7. Log out and log back in. User should again have access to the library bundle collections.

Screenshots of your changes (if appropriate):

User is bundle eligible and has agreed to the terms of use

User is bundle eligible but has not agreed to the terms of use

User is bundle eligible, has not agreed to the terms of use, logged out and logged back in

Types of changes

What types of changes does your code introduce? Add an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

[jsnshrmn]

I'd call TWLight.users.helpers.editor_data.editor_bundle_eligible() and update the editor's eligibility upon accepting terms. Other than that and one inline comment, this is looking good!

[jsnshrmn]

Looks good!