Extend Dashbuilder Components to support internal components.

External Components currently serve files from a directory configured by user and it works great. In order to provide internal tested and approved components it is required to have an internal structure with the tested components. 

Components Project:

• Create a Maven project that supports web tools, just like it is done with appformer-js;
• This is a backend project, with web artifacts;
• External component assets provider, the class that is responsible to load components assets, should then look also these internal components to server assets;

Loading Components:

• Make sure that ExternalComponentsLoader is aware of internal components - possibly break components loaders in two: external and internal;
• It should simply change where the file is being loaded from, the logic of using manifest.json and more would be the same

In client side:

• A category for internal components should be created in components pallet 
• The same drag component and all the client logic would stay the same

In Dashbuilder Runtime

• Pay attention to components in multi mode - internal components should NOT be partitioned 

Acceptance Criteria

• A "logo" component should be available as internal component
• A page with this internal component should be exported and imported in Dashbuilder Runtime - mainly in multi mode