[ADVAPP-185] & [ADVAPP-186]: Enforce license relationship for Retention CRM with respect to students / prospects

[danharrin]

Ticket(s) or GitHub Issue

• https://canyongbs.atlassian.net/browse/ADVAPP-185
• https://canyongbs.atlassian.net/browse/ADVAPP-186

Technical Description

License checking is mainly done in policies and scopes, but there are some exceptions when business logic comes into play.

The test suite has not been adapted for this changes yet. The tests have not been updated. However, since this is a large PR, it might be good to start reviewing, and then just don't merge until those are passing later today.

Types of changes

What types of changes does your code introduce? Put 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)
• Content or styling update (Changes which don't affect functionality)
• DevOps
• Documentation

Screenshots (if appropriate)

Any deployment steps required?

A deployment step could be a command that needs to be executed or an ENV key that needs to be added, for example.

• Yes, please specify
• No

All users must have licenses. This has been added to the super admin seeder.

---

Before contributing and submitting this PR, make sure you have:

• Read the contributing guidelines.
• Title the PR with the ticket/issue number and a short description of the changes made. Or if no ticket/issue exists, title the PR with a short description of the changes made
• Linked a relevant ticket or issue or describe the issue/feature which this PR resolves/implements.
• Resolved all conflicts, if any.
• Rebased your branch PR on top of the latest upstream develop branch.