Feature/resolve split package osgi

[JulianFeinauer]

This PR brings full OSGi support to PLC4X.
A bundle for the S7 driver is also added.

[JulianFeinauer]

Its not intended to be merged, yet its. First, we should check it in-depth.

[chrisdutz]

Hi Julian,
I think it would have been better to rename things from:
org.apache.plc4x.java.base.connection
To:
org.apache.plc4x.java.connection.tcp
org.apache.plc4x.java.connection.serial
org.apache.plc4x.java.connection.mock
...
as it sort of gets more and more concrete further down the package ...
What do you think? cause the way you currently have it, it's sort of an empty "connection" package for every type.

[chrisdutz]

Hi Julian,
I think it would have been better to rename things from:
org.apache.plc4x.java.base.connection
To:
org.apache.plc4x.java.connection.tcp
org.apache.plc4x.java.connection.serial
org.apache.plc4x.java.connection.mock
...
as it sort of gets more and more concrete further down the package ...
What do you think? cause the way you currently have it, it's sort of an empty "connection" package for every type.

[JulianFeinauer]

And I agree with you @chrisdutz with the naming. I just wanted to make the smalles changes possible which was base -> xxx.

[ottobackwards]

How about throwing in a readme in the karaf features area?
I would have expected to see some documentation around OSGI support as well at the top level somewhere

[chrisdutz]

We already had "plc4j/integrations/apache-karaf" modules and there we were using the goal "features-generate-descriptor" which generates the "feature.xml" ... the way you're currently doing it would require to manually maintain a second resource with dependency information.

[chrisdutz]

Ok ... I compared the feature.xml you added manually, that's identical to the one generated by the plugin, except that it has one additional entry: scr