#47 Config for game version - 1.0,1.1

[Mark Gibson]

the game adapter is now dealing with game from both
game 1.0 and 1.1 - but there isnt really a formal
configuration for this - there is DO-ONE-LEVEL-ANNOTS
but that only covers one level annots and should be
phased out anyways (one levels configged in tiers file)
There needs to be a configuration:

GameVersion "1.0" or 1.1...

Whats new in 1.1:
one level annots
synonyms with owner attribute

possible other 1.1 things:
synonyms with internal attribute (todo)
annotStatus field as a more generic way of dealing with
status - new way for sp_status property

I think on reading the game adapter should be as
flexible and backward compatible as possible - so no
matter how configured read in whatever shows up in the
game file (and perhaps print a message). But on writing
it should probably adhere to the version.

So for instance if we are configged for 1.1, and theres
a 1 level annot that has 3 levels in game it should be
read in anyways(and i think the game adapter chokes on
this at the moment - it reads it in but as a faulty 1
level annot with a ridiculous range). on writing it
should be written with 1 level (so it actually will be
converted). The other question is on reading such into
apollo datamodel would it get 1 or 3 levels - as first
cut it could be 3 - but it would be nice to convert to
1 eventually on read.