Issue #2: move ZnServerStarter to the Zinc project
Issue #2:

- rename Application-Server-Tools to GsApplicationTools-Server and do a bit of restructuring
- add test package and test stub
Issue #2: correct mistakes in baseline for package renames
Issue #2: load CI group to pick up tests
Issue #2:

Taking approach where instead of subclassing GemServerStarter, subclass GemServer ... then we can do direct customization of the various bits and pieces that need customization on run ... and pass any interesting state via the script call ... script location etc. can be specified by the subclass ...

Added tests for validating the basic api
Issue #2: incorporated the "server boilerplate" Smalltalk code from startSeaside30_Adaptor ... push a bunch of stuff around ...
Issue #2: remove the GemServerStarter classes .... refactor start logic to send startGems, restartGems and stopGems directory to the GemServer instance ... return GemServer instance when created, so that inline start and stop logic can be done without requiring lookup...
Issue #2: get rid of GemServer portInstance variable ... not really necessary
Issue #2: get tests passing?
Issue #2: continue move towards GemServer centric design ... with  GemServer class>>register:for:on: as the center piece
tweak travisCI.st test
Issue #2: get ready to run scripts ... add test
[ci skip] fiddling with scripts
[ci skip]high diddle diddle, another script fiddle
issue #2: [ci skip] checkpoint .. preparing for first script tests
Issue #2: start/stop/restart appears to be working but I don't like the level of feedback ... need status command that looks at pid and verifies that pid is there and perhaps some other status information...
Issue #2: adjustments for testing
Issue #2: add remote vm test
remove the unneeded scripts [ci skip]
Issue #2: get the GemServerRemoteVMTests>>testStart test to function