Prepare UI/UX when monetisation transition period ends (cut-off)

What should happen when monetisation transition period ends.

1. Instance admin checkbox continues to exist as a way for customers to deactivate code suggestions;
2. we will need to update the legal language.
3. The checkbox becomes enabled and defaults on once a customer has purchased at least one add-on seat.
4. Proposal: The checkbox is disabled (grayed out) if the customer has not purchased at least one add-on seat
5. Proposal: In case there is no token or purchased code suggestion seat, we tell the customer that he needs to purchase the add_on (with the proper link), and in case they already did, to re-sync the license manually (show refresh button or send the customer to license page to refresh)

It would be nice if we could have 4. and 5. released earlier, so when CDot does not return the token (because the customer doesn't have an addon) we show the proper message and gray out the checkbox/toggle even in older Gitlab versions. At the moment, CDot always returns the token if the license is valid.

Example: The customer is running 16.5. We do the cutoff several releases later. After cut-off Cdot will stop returning tokens to SM instance, We still show proper message that code suggestions are disabled, and that the customer needs to buy an add-on