Install SAP libs in the Maven local repository

[johnpoth]

(cherry picked from commit 41a50e0)

rebase from fusesource#37

@cunningt hope this is ok. I'll copy paste the original comments here for ease of use:

As we discussed, this is a PR that demonstrates users installing the three SAP libraries in their Maven repository instead of using a lib folder. So for example using version 3.1.4 for sapjco and 3.1.1 for sapidoc on Linux x86 64 bit the user would have to run three commands:

1. mvn install:install-file -DgroupId=com.sap.conn.jco -DartifactId=sapjco3 -Dversion=3.1.4 -Dpackaging=jar -Dfile=sapjco3.jar

2. mvn install:install-file -DgroupId=com.sap.conn.idoc -DartifactId=sapidoc3 -Dversion=3.1.1 -Dpackaging=jar -Dfile=sapidoc3.jar

3. mvn install:install-file -DgroupId=com.sap.conn.jco -DartifactId=sapjco3 -Dversion=3.1.4 -Dclassifier=linux-x86_64 -Dpackaging=so -Dfile=libsapjco3.so

Some drawbacks compared to using the lib folder strategy:

1. If the user uses a different version for sapjco or sapidoc, he has to update the pom.xml
2. The command for the native library is OS dependent so error prone. If a different classifier was used the pom.xml also has to be updated.
3. The standalone version of the quickstarts (not sure if we should keep them here or not as this is for SpringBoot) uses the Camel Maven Plugin which doesn't have an option to add extra dependencies. We would therefore have to use the lib folder strategy.

Given those drawbacks I think I prefer keeping the lib folder strategy but maybe I'm missing something. We can improve on it as @luigidemasi suggested and use a single lib folder too.

Let me know what you think!

[Croway]

I am afraid that documentation in these quickstart will be pretty much lost.. would it be possible to provide this (or similar) documentation to the doc team? so that it can be published downstream?

[cunningt]

I am afraid that documentation in these quickstart will be pretty much lost.. would it be possible to provide this (or similar) documentation to the doc team? so that it can be published downstream?

Talked to Federico about this - I think we're okay here. The only doc-related changes here are README.md formatting changes and changes to the product name ("JBoss Fuse" -> "Red Hat build of Apache Camel"). I think the documentation around SAP that the doc team would need is all in jboss-fuse/fuse-components and to a smaller extent the camel-sap-starter in camel-spring-boot.