[#PETALSESBCONT-225] Move the autoloader as an extension of the Petals ESB container - Petals Link JIRA

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-242~~ The Autoloader does not require the AdminService
~~PETALSESBCONT-243~~ Improve Fractal component-based architecture of the Autoloader
~~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-235~~ The autoloader implementation uses a child class of the repository implementation
~~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-229~~ Create a Debian package to install the Petals ESB Autoloader

Petals ESB Container