Fixes #1631 Adding a non binding ProtocolSocketFactory impl

Motivation:
The reason for this ProtocolSocketFactory implementation is
that for ProxyServlet we don't need to bind to a local address and port.
This binding can cause issue in PaaS environments where restrictions apply.

When HttpConnection's open method calls ProtocolSocketFactory's
 createSocket(String, int, InetAddress, int, HttpConnectionParams)
which by default will use DefaultProtocolSocketFactory's
 createSocket(String, int, InetAddress, int, HttpConnectionParams).
The method that will be invoked will be DefaultProtocolSocketFactory's
 createSocket(String, int, InetAddress, int)
which will call
  return new Socket(host, port, localAddress, localPort);
The above constructor will create a new Socket and connect to the
remote address and port (the first two arguments). It will also
bind() to the local address and port. This is the part that can
cause issue in PaaS environment where there are restrictions.

Modifications:
Provide a NonBindingSocketFactory that ignores the local address and
port avoiding binding to a local address.

Result:
The ProxyServlet is usable in PaaS environments without additional
configuration required by users.
#1610: Include quickstarts in fabric8-karaf distro.
#1607 - updating quickstart readme instructions
#1607 - updating quickstart readme instructions
Added missing gitignore for new example
#1638: Updated readme instructions how to build from source code.
quickstarts should use same profile name as out of the box, as then its the same installation procedure in fabric if you deploy pre-build or build from source and use fabric8:deploy.
#1638: Quickstart instructions how to build from source and upload to fabric with fabric8:deploy.
#1604 renames the containers-java.debug profile to be just containers-debug as we should be able to use this profile with any container
moved the camel-spring-java example into the quickstarts and renamed the eip-dozer-wiki to be camel-dozer-wiki which feels a better name; folks are more likely to know camel than acronyms
moved the camel-spring-java example into the quickstarts and renamed the eip-dozer-wiki to be camel-dozer-wiki which feels a better name; folks are more likely to know camel than acronyms
default to using tomcat for wars; since thats the most popular servlet container and most likely to work based on previous experience of wars and karaf/wildfly ;). folks can easily specify the one they want though if this guess isn't the best
expose the debug port by default for tomcat/tomee
add a weld java profile #1644
auto default to weld for java projects using CDI #1644
add a camel cdi quickstart using the java container, fixes #1644
add a camel cdi quickstart using the java container, fixes #1644
removed cruft
added archetype for camel-cdi-java
add archetype for a camel cdi quickstart using the java container, fixes #1644