feat: [FC-86] Added support for the new Catalog MFE

[PKulkoRaccoonGang]

Description

This PR includes the configuration for the new Catalog MFE (Verawood release).

PR with an installation example for the Catalog MFE as a Tutor plugin - openedx/frontend-app-catalog#60

How Has This Been Tested?

1. Clone this repository
2. Use the local version of this tutor plugin
3. Rebuild the mfe image
4. Go to http://apps.local.openedx.io:1998/catalog/

Merge Checklist

• If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Sandbox, if applicable.
• Is there adequate test coverage for your changes?

Post-merge Checklist

• Deploy the changes to prod after verifying on stage or ask @openedx/edx-infinity to do it.
• 🎉 🙌 Celebrate! Thanks for your contribution.

[DawoudSheraz]

Hi, isn't this a repeat of #257?

[PKulkoRaccoonGang]

@brian-smith-tcril I’d like to kindly suggest taking a look at this PR. We can merge it a bit later, once everything is ready. Would that work for you?
Unfortunately, I don’t have the permissions to add you as a reviewer directly.

[brian-smith-tcril]

Overall the changes here make sense, but I think we might need some minor changes to the logic.

I noticed

tutor-mfe/tutormfe/patches/openedx-lms-common-settings

Lines 11 to 13 in ca0665f

	{% if get_mfe("catalog") %}
	FEATURES['ENABLE_CATALOG_MICROFRONTEND'] = True
	{% endif %}

looks almost identical to

tutor-mfe/tutormfe/patches/openedx-lms-common-settings

Lines 8 to 10 in ca0665f

	{% if get_mfe("authn") %}
	FEATURES['ENABLE_AUTHN_MICROFRONTEND'] = True
	{% endif %}

and

tutor-mfe/tutormfe/plugin.py

Lines 75 to 78 in ca0665f

	"catalog": {
	"repository": "https://github.com/openedx/frontend-app-catalog.git",
	"port": 1998,
	},

is being added to CORE_MFE_APPS.

This makes me think that this PR is putting the catalog MFE in a "default on" state. For Ulmo, the goal is to allow site operators to switch from the legacy catalog to the Catalog MFE, but not default to it.

@arbrandes - do you know how we've handled this in the past?

[arbrandes]

@brian-smith-tcril, in the past the optionality of an MFE came down to either it being defined in an optional plugin (like Learner Record via tutor-credentials), or a feature/waffle flag.

Because of the nature of the Catalog MFE (particularly, the fact it's the first thing anybody sees, also people can use it logged out), I think the best thing is to go via a plugin.

[PKulkoRaccoonGang]

@brian-smith-tcril, in the past the optionality of an MFE came down to either it being defined in an optional plugin (like Learner Record via tutor-credentials), or a feature/waffle flag.

Because of the nature of the Catalog MFE (particularly, the fact it's the first thing anybody sees, also people can use it logged out), I think the best thing is to go via a plugin.

Thanks! I have a question and would appreciate your thoughts. Since the Catalog MFE isn’t part of another service (like tutor-credentials) and we have FEATURES['ENABLE_CATALOG_MICROFRONTEND'], would it make sense to simply set this flag to False and add a few notes in the tutor-mfe documentation?

This way, the Catalog MFE would be disabled by default but could still be enabled if needed. Please let me know if I’m misunderstanding anything.

[kyrylo-kh]

Looks good to me!

[arbrandes]

Looks good to me!

[arbrandes]

@regisb, any objections? Anybody else at Edly I should be asking?

[arbrandes]

Going ahead and merging this so people can give early feedback.