These 2 tests were flawed. They depended on a unit receiving direct contacts after it had been  detected and quarantined, which violated this statement from the model spec: "Quarantined units cannot be involved in direct contact". The tests have been rewritten to use indirect contact.
Fix: resources and implementation of controls module should be instantiated whenever detection is in use. The resources module is the one that sends out a PublicAnnouncement event at the first detection, which can then influence the probability associated with later detections and start the effect of movement control charts.
Changes to test description file; should have been part of last check-in.
xml2sqlite script now reads in-zone movement control charts from the XML.
Updated some test cases that depended on a very old behavior of ring vaccination: detected infected units would be vaccinated, but not the one that triggered the ring. Starting at version 3.2.12, checkboxes were added to the GUI to choose whether to vaccinate detected infected units (including the one that triggered the ring) or not vaccinate detected infected units. From that version on there was no way to achieve the "old" behavior via the GUI.