Script can handle being saved to a state and then relaunched from that state

[thebgpikester]

GOAL:
To support DAWS state saving by making the script handle a session restart.

BENEFIT:
DAWS can be added over the top, the script can continue to work with long routes and long gameplay. Sessions can restart and the script picks up where it left off as best as possible with a different initial mission set but orders the gorups the same way nonetheless.

METHOD:
Using the group scan described in #57 should catch most of this.

POTENTIAL ISSUES:

1. The TF or group will have an initial characteristic in one mission, but on the next, may not pick up the same one. IE, group 1 is headed for Zone 1 as part of TF1 with off road, speed 11, skill avg. However when the server restarts the default characteristics may pull it out of the original TF and give it some default characteristics like going to zone 2, or nowhere. I suggest doing a naming per TF and attaching the name to the objective/TF
2. Spawned units outwith the TF schema are already in an unknown state due to Add alternative to specifying units #57 and another issue. Need to make sure they don't suddenly swap their objective.

[thebgpikester]

Currently still AutoGFT won't work after a map save and reload due to the original name of the spawned group changing in between spawns, which means AutoGFT won't recognise a group moving and seize control of it. What it will likely do is just spawn some more and the oiriginal group will go to the end of it's currently saved route and stop forever.