Closes#2904
Things aren't named quite right yet but here's a start! I plan to add to this but wanted to share early.

requirements as I understand them:

• license data must be fetched on app mount (which means also on browser refresh)
• license data must be fetched any action that could cause compliance (user suspension, upgrading, disabling a feature) or change what's enabled
• whenever warnings are present in the license data, the LicenseBanner must be shown on all pages containing all warnings
• all features that areenabled in the license data must be available (soft enforcement)
• all paid features must be unavailable to OSS users - I have kind of handled this by defaulting license data toenabled: false, but we should decide how the API will handle this case
• there will be an admin page containing toggles for enabling/disabling all paid features. This page will be available to all non-OSS admins. Defaults will not handle this case so we should sync on a way for the frontend to know if they should get this page.
• the toggle for any paid feature for whichentitled isfalse will show a warning, but the admin will be able to enable the feature (soft enforcement)

Solution:

• licenseXService fetches license data on app mount, refresh, and various events and holds license data in global state
• LicenseBanner displays any warnings
• LicenseRequired page wrapper redirects OSS users to another page (currently 404, will later be something more informative) if they try to access a page that is entirely a paid feature
• pages select visibility booleans fromlicenseXService to determine whether to show smaller features (coming next)