add -ccj command line arg and clone_cloud= params as alternate ways of starting a cloud clone (command line can be used to override a test that normally builds a cloud, so all tests can run as-is. Also, michal could pass a clone_cloud param in the ec2 config.json, so that they can do that on ec2/jenkins also (you can't use command line args with nosetests. But a clone_cloud config bit, like the s3n import folder redirect bits, must be possible/manageable