feat: restricted runs to be considered conditionally active

[iloveagent57]

Restricted course run records will be set with is_marketable: false from the upstream source-of-truth (course-discovery). But because our discovery <-> catalog synchronization has business logic that filters course run json metadata (inside of courses) to only the allowed restricted runs for a catalog, we can safely assume when looking at a course run metadata record in the context of a catalog, if that run has a non-null, B2B restriction type, then it is permitted to be part of the catalog and should be considered active (as long as it is published and enrollable).

Post-review

• Squash commits into discrete sets of changes
• Ensure that once the changes have been deployed to stage, prod is manually deployed