Story

Add a new frontend application in the RHDH build, that can be selected instead of the old frontend during yarn start.
It should:

• be based on the dynamic frontend plugin support merged upstream,
• use dynamicFrontendFeatureLoader,
• at start only load dynamic plugins that were migrated to the new frontend system (== having a new frontend system plugin or module exported as default export in the alpha API),
• include the default upstream core plugins such as catalog, search, etc..., added statically, but those would be overridable through additional new frontend dynamic plugins.

The RHDH backend should allow using either the new frontend easily, while the old frontend would still be the default and use in production.

Background

Dependencies and Blockers

QE impacted work

Documentation impacted work

Acceptance Criteria

upstream documentation updates (design docs, release notes etc)

Technical enablement / Demo