Dynamic Plugin needs to be externally consumable - package.json exports

As an adopter of the @openshift-console/dynamic-plugin-sdk I want to easily integrate into my development pipeline so that I can extend the OCP console.

Trying to pull in the dynamic-plugin-sdk into ACM is proving to be problematic. We would have to move to older dependencies. Integrating with webpack and typescript requires a very specific setup.

The dynamic-plugin-sdk has only really been used internally by OCP and is strongly tied to the setup and dependencies of OCP. For the dynamic-plugin-sdk to be externally consumable by adopters, it should be as easy to use as other webpack plugins such as HtmlWebpackPlugin or CompressionPlugin.

Acceptance Criteria

• Includes it's own dependencies - does not require adopters to include those dependencies
• Does not require extra configuration such as tsconfig paths - other webpack plugins do not require this and forcing it is not developer friendly
• Should be able to be used with TypeScript - do not use package.json exports until it is supported
• The dynamic demo plugin should be updated to use newer dependencies and use the plugin without a bunch of tweaks to tsconfig paths. 

Currently

• uses package.json exports
  • this should not be used until it is fully supported - TS does not
  • this makes it so that TS config paths must be configured and does not work with newer versions of dependencies