Set edx.org theme as default for edx-platform and MFEs

[mfarhan943]

Description:
Automate setting the edx.org theme as the default for both the edx-platform and MFEs during devstack provisioning.

Related Ticket:
edx/edx-arch-experiments#824

[adamstankiewicz]

Given MFEs can define the brand package (and its installed version) independently across each MFE, are there any alternative ways of setting the PARAGON_BRAND_PACKAGE on a per-MFE basis?

For example, frontend-app-learning might want to use v3 of the brand package whereas frontend-app-learner-dashboard might want v2. As is, I believe this would use the latest version of the package, regardless of compatibility with the consuming MFE. This MFE-specific support would largely reflect how brand package MFEs are configured via edx-internal today.

Perhaps each MFE configured via docker-compose.yml, extending microfrontend.yml, could define it as an environment variable that can be consumed by microfrontend.yml?

[adamstankiewicz]

[curious] Should the PARAGON_BRAND_PACKAGE be defined as the full NPM module's name? It seems like the @ is concatenated within microfrontend.yml vs. included in the PARAGON_BRAND_PACKAGE definition.

Any reason this couldn't be @edx/brand-edx.org here, to representing the full NPM module name vs. splitting it across multiple files? For example, what if we ended up using a brand package that wasn't associated with an organization, i.e. not prefixed with @ (unlikely but demonstrates the question)?