Replacing spring-bundlor with maven-bundle-plugin

The querydsl-root project has two properties:

 - __osgi.import.package.root:__ Import package definitions that are common to all projects
 - __osgi.import.package__: The value comes from the root by default. This property is specified in maven-bundle-plugin. This property is overridden in modules where special package import settings are necessary.

The Import-Package definitions are different than the ones that spring-bundlor-plugin generated. They are strict. More about the version policy of bnd: http://www.aqute.biz/Bnd/Format#versionpolicy

I tried to keep the Import-Package headers as compatible as possible. There are differences, however:

 - Packages from projects that follow [semantic versioning rules][1] are imported in the way how the maven plugin imports them by default
 - Packages from projects that do not follow the rules are imported in the way that the lowest accepted version is the one that is offered by the dependency
 - Packages from dependencies that have no OSGi MANIFEST headers are imported with no version (means version "0.0.0"). The reason is that the version of the dependency does not always meet the version of every package in the bundle. Good example is the osgi jar itself where almost every package has a different version as they meet the rules of semantic versioning.

Please let me know if you like it! For me the most important is to make the optional dependencies optional (especially spatial imports in the sql module) as I cannot use the querydsl jars since 3.4.0 in my OSGi environment.

Some lines are changed as windows/unix enters were mixed in pom files.
After change all of them are unix characters.

[1]: http://semver.org/
I packaged all of the jars before changing the configuration. In the original MANIFEST I found this:

    org.apache.lucene.search;version="[3.0.0,3.1.0)"

That is why I specified the same version range. Probably the version range is wrong in the original MANIFEST as well.