[#PETALSESBCONT-226] Move the artifact repository as an extension of the Petals ESB container - Petals Link JIRA

Description:

The artifact repository is not a required internal component to run the Petals ESB container. So it can be provided as an extension.

Depends

This issue depends on:
~~PETALSESBCONT-231~~ Replace the internal JMX client stack by petals-jmx-api
~~PETALSESBCONT-232~~ The configuration service has not to depend on the Kernel WS API
~~PETALSESBCONT-236~~ 'ServiceAssemblyLifeCycle' is a fractal component, not a simple class
~~PETALSESBCONT-248~~ The 'Installer' is a Fractal component and it MUST be accessed by its interface
~~PETALSESBCONT-233~~ The configuration service API must throw its own exceptions
~~PETALSESBCONT-234~~ The topology service must throw its own exceptions
~~PETALSESBCONT-239~~ MBeanNameImpl should be a Fractal component
~~PETALSESBCONT-240~~ The composite "JBI-Messaging" required the not used client interface "admin"
~~PETALSESBCONT-244~~ The component 'Transaction' should be a subcomponent of the composite 'System'
~~PETALSESBCONT-245~~ The component 'LoggingService' should be a subcomponent of the composite 'System'

This issue blocks:
~~PETALSESBCONT-214~~ Create a Debian package to install Petals ESB
~~PETALSESBCONT-230~~ Create a Debian package to install the Petals ESB Artifact Repository
~~PETALSESBCONT-249~~ Move the WS API as an extension of the Petals ESB container

Petals ESB Container