create scripts for building a TodeClient/st_launcher/Rowan development stone, where TodeClient port will take place

[dalehenrich]

Part of Issue #260.

• create an issue_260 branch for GsDevKit_home
• add Rowan, st_launcher, and stash to the list of standard projects to be cloned. These projects are needed to build/rebuild the gsdevkit solo extent
  • Rowan needs a gsdevkit_launcher branch, as Rowan API will evolve independent of the gsdevkit_launcher project. st_launcher and stash will evolve in synch with gsdevkit_launcher.
• set up the basic scripts that are needed to start development...
  • gsdevkit_launcher (embedded project) - gsdevkit_topaz_launcher is the GsDevKit_home aware script launcher. Based on st_launcher.
    • convert interpreter to use gsdevkit_launcher topaz solo extent
    • convert gsdevkit_launcher script execution code to run directly in topaz solo extent without needing an image name
    • consider loading tonel class file without leaving dummy project around (grab class and unload dummy project perhaps?)
    • AbstractGsDevKitProgram created ... this is where the CommandLine logic will be located
    • filetree format scripts repository -- use tODE to develop scripts
    • rowan scripts for converting back and forth between filetree format script classes (in gsdevkit_launcher/src) tonel format files (in $GS_HOME/alt_bin)
  • $GS_HOME/gemstone is home to topaz solo extent and ???
  • $GS_HOME/alt_bin is where the new replacement scripts will go ... use alt_bin to allow swapping in/out of new scripts
    • $GS_HOME/alt_bin/gsdevkit_launcher functional
    • $GS_HOME/alt_bin/gsdevkit_topaz_launcher functional
  • gsdevkit_launcher development stone creation scripts
    • bootstrap script to install pre-built topaz solo extent (bash script)
    • script to create a deployment/development stone. tODE + Rowan + gsdevkit_launcher support plus script for deploying a topaz solo extent
    • replace current gsdevkit_home tests with gsdevkit_launcher script tests
• example script that translates one of the existing commandLine scripts to produce help text and options/argument handling ... no need for meat yet ...
• send mail to this list and we can start farming out tasks