package the rest service with components in a maven repo

2 points.
1) to be able to run IO component from the REST apis we need to package the API, the definition together and the runtime in some maven m2.

2)The components used by the tcomp REST APIs should be shared with other services such as the runtime of beam.
so the artifacts for defining the components and their associated runtimes should be packaged in some sharable way for both TCOMP rest apis and other services requiring those components to avoid duplications.
The proposed solution would be to package them as a maven repository (.m2).

This implies that the launch of the tcomp rest API will have to be tweaked to have those components located in the maven repo to be in the scanning classpath of the app.

We also need to provide a zipped package along with .sh and .bat to launch the service.