feat: v2 catalog contains_content_items view

[iloveagent57]

1. Set up restricted content metadata in a catalog as described here: feat: sync full metadata for restricted courses #985
2. Observe that GET http://localhost:18160/api/v1/enterprise-catalogs/7467c9d2-433c-4f7e-ba2e-c5c7798527b2/contains_content_items/?course_run_ids=course-v1%3AedX%2BDemoX%2Brestricted_run does not contain your restricted run.
3. Observe that the v2 endpoint http://localhost:18160/api/v2/enterprise-catalogs/7467c9d2-433c-4f7e-ba2e-c5c7798527b2/contains_content_items/?course_run_ids=course-v1%3AedX%2BDemoX%2Brestricted_run does contain your restricted content.

ENT-9408

Post-review

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

[pwnage101]

Nice refactor 👍

[pwnage101]

Nit: the top-level key under the restricted_runs_allowed key should actually be an aggregation key, which means you should prefix this with "course:". It's merely a formality for this test suite, but I think important for people who might ever need to touch this test or refer to it as a code reference.

[iloveagent57]

It can actually be a regular course key or an aggregation key, the code is flexible about it:

enterprise-catalog/enterprise_catalog/apps/catalog/models.py

Lines 117 to 137 in 5425510

	@cached_property
	def restricted_runs_allowed(self):
	"""
	Return a dict of restricted course <-> run mappings by
	course key, e.g.
	```
	"edX+FUN": [
	"course-v1:edX+FUN+3T2024"
	]
	```
	"""
	mapping = self.content_filter.get(RESTRICTED_RUNS_ALLOWED_KEY) # pylint: disable=no-member
	if not mapping:
	return None
	if not isinstance(mapping, dict):
	LOGGER.error('%s restricted runs value is not a dict', self)
	return None
	return {
	course_key.removeprefix(AGGREGATION_KEY_PREFIX): course_run_list
	for course_key, course_run_list in mapping.items()
	}