save and restore in AWS + CloudShell

[alonagetzler]

AWS:

• orchestration_save that creates snapshot in AWS and returns blueprint with apps pointing to new AMIs
• orchestration_restore that removes the old instance in AWS, deploys a new AWS instance using the AMI and calls an API to populate the VM properties. the new instance should get the same private and public IP, same SG (open ports), same tags, (TBD - additional storage + custom tags)

CloudShell:

• Save snapshot json object in server as a part of the reservaiton information. This instance should be copied to an environment created from the reservation. Information should also be included in export/impoirt
• Where deleting an environment, the server should asynchronously delete all snapshots associated with it
• Snapshot blueprints will have a 'snapshot' property and a 'original_blueprint' property linking of the blueprint it came from. The 'original_blueprint' information will be saved in sisense. Both should be available in importa/export
• Add a new 'update_vm_details' API to use in save/restore

[pascaljoly]

The CloudShell part looks to me something we should have as part of the general Snapshot and Restore template, not just for AWS.