DBSteward 1.3 API change - XML format changes
remove database host and name
restructure slony replica definitions for multiple set definitions
first pass of slony replication multiple slonyReplicaSet conversion

node definitions in fallback mode where replicated tables and sequences do not have a slonySetId

included are updates to make tests/pgsql8/DuplicateSlonyIdsTest.php suite pass
add --generateslonik mode to only generate slony slonik commands for subscription and upgrades when it has been asked for
prefix upgrade files with the name of the top level definition file they are for, same as full _build.sql files
pass and announce the replica set being processed during pgsql8 slonik upgrade script generation
match slonyNode and slonyReplicaSetNode by id ( DBSteward 1.3 API )
match slonyNode and slonyReplicaSetNode by id ( DBSteward 1.3 API )
refactor slonik upgrade script content generation to be replica set specific and to use the DBSteward 1.4 API XML schema
summarize slonyId segments for the compiling user
accurate id listing when the last number in the list is not part of a run
when --generateslonik is specified during pgsql8 upgrade differencig, setup pgsql8_diff to detour off of sql99_diff and manage its sql output files per slony replica set id
ofs router by replica set ID for multiple replica sets in a single pgsql8 + slony definition