Expose all of core PatternFly for dynamic plugin use

Currently, webpack tree shakes PatternFly and only includes the components used by console in its vendor bundle. We need to expose all of the core PatternFly components for use in dynamic plugin, which means we have to disable tree shaking for PatternFly. We should expose this as a separate bundle. This will allow browsers to cache more efficiently and only need to load the PF bundle again when we upgrade PatternFly.

Open Questions

What parts of PatternFly do we consider core?

Acceptance Criteria

• All PatternFly core components are exposed to dynamic plugins
• PatternFly is exposed as a separate bundle that is not part of the main vendor bundle

cc christianvogt vszocs@redhat.com jcaiani@redhat.com jtalton