Solution: add a workaround to reinstall libtool. Travis hasn't fixed
the issue in a month, so time for a little hack until they sort it.

Solution: Use travis to deploy these artifacts automatically.

The deployment is triggered by tagging on the zeromq/libzmq repository.
Of the many builds travis is checking only the default one with
libsodium and drafts disabled is used for deployment.

For now the results of `make distcheck` are deployed as well as their
md5 and sha1 hash sums. Further changes may upload a generated
Changelog as well.

Solution: do default test with DRAFT APIs enabled

Solution: add one test run in a docket container environment, which
is currently the only environment where it's possibile to bind a
socket to ::1.

Solution: run Travis CI in newer Trusty (14.04 LTS) release.

Solution: run Valgrind only on the default Linux build to avoid
increasing the runtime.

Solution: add new coverage build, and upload results to coveralls.io

Solution: remove libsodium and no curve builds from cmake and android

Solution: establish a matrix of CI options. On one axis we have the
build system (autotools, cmake, android) and on the other axis we
have the encryption options (tweetnacl, libsodium or none).

Solution: build by default with tweetnacl, and add sub-build project
to test libsodium

Solution: add builds/cmake/ci_build.sh and call it from travis.yml

Solution: add builds/tweetnacl/ci_build.sh and add it in travis.yml

Solution: change .travis.yml to build "android" instead of "qt-android"

OSX does not ship with binutils, need to install it before the script
run via brew in order to be able to use greadelf, needed by the
qt-android CI script.

Test cases occasionally fail, especially on OSX, due to socket limit.
Part of fix for #1502

Solution: Fix the qt-android build

Solution: Add qt-android build system and add to travis-ci