For Fuse Online asses what we distribute in MRRC and offline manifests

In the maven.repository.redhat.com we distribute a number of io.syndesis artifacts, these also go in the offline manifest to be used by the offline tool.
This generates a larger support area and has an impact on the build itself (performance, storage).
We should not be distributing most of those artifacts as they are not consumed via Maven. For example the fat jars of server and meta components are not useful there at all, but there are many more artifacts that have no use there.
We should limit the artifacts we distribute to the artifacts that are needed to build an extension.
Most likely we should review what gets published during a PNC build and make adjustments to component POM files that unneeded components are not published.
This is of interest upstream as well, so analogous change can be made there first.