Fix bug in autoscaling test. I was not waiting for initial instance to launch before changing capacity. It used to work but we did see failures sometimes. We really should wait for scaling to complete before making more changes.  The test is for changing launch configs and the test performs as it should now. We may have exposed a performance regression (one that had been "felt" in 4.0) with new ServSep architecture. Or perhaps there are messages being lost when actions are fired too close together.

This change also has some extra debug for ELB Stickiness test.
Fix cleanup_artifacts for more than a single reservation