Synchronize with Zinc 2.4.3

Sven,

I took the liberty of copying the packages that comprise Zinc 2.4.3 up to the glassdb fork of zinc.

In pulling the packages up to github I [created a pharo1x branch for the Zinc-Patch-HTTPSocket-SvenVanCaekenberghe.1 package](https://github.com/glassdb/zinc/commit/de3b7c018a6daa660f8cc861093114aab661ca61) since pharo-2.0 uses a different version of the same package. Besides the fact that I only want to store a single version of any package in the git repository it makes managing the monticello files easier if all the pharo1.0 code is identified by a monticello branch ...

I also added a [BaselineOfZincHTTPComponents] (https://github.com/glassdb/zinc/commit/01f8dd0169aa9181c8400624f5cc07541ee44697) which is how you manage configurations in a git repository.

Finally i added TravisCI support which is basically a [.travis.yml](https://github.com/glassdb/zinc/blob/master/.travis.yml) file and a [travisCI.st](https://github.com/glassdb/zinc/blob/master/tests/travisCI.st) test driver file. With those files (and a [TravisCI](https://travis-ci.org/) account). Builds are automatically run against each push/pull request for a repository. For example, here's the [build results for the commit leading up to this pull request](https://travis-ci.org/glassdb/zinc/builds/8696622). For your code base, I've got builds run against Pharo-1.3, Pharo-1.4 and Pharo-2.0 ... travis ci support for Pharo-3.0 is in the works ...

Anyway, shortly we will begin the work of porting Zinc 2.4.3 to GemStone.... It took awhile, but we just [finished up the port of Zinc 2.3.2 to GemStone](https://github.com/glassdb/zinc/releases)...

Dale