Consolidate labs (adv design & basic) under Cloud9 IDE + add provisioning into EE blueprint

[aiziumov]

1. In Adv design patterns labs scripts are reviewed via EC2 that is provisioned - it'll be better to leverage Cloud9 IDE from basic labs here - to provide better UX for end users when reviewing the python scripts
2. Add EE module provisioning for VPC/Cloud9 (currently you need to download and run CFn on your own and setup C9 env manually) - to provide more smooth end user experience. If we have python code in Public gitrepo - we could even auto-clone that into C9 during provisioning as well.
3. Internal labs inside AMZN needing to be updated

[switch180]

Also:

Many people were confused on this step when we load 500 rows just within 17seconds * 5. (https://amazon-dynamodb-labs.com/design-patterns/ex1capacity/step2.html) It took me a while to figure out that we're leveraging underused Provisioned capacity here for the last 1-2 minutes. But IMHO for self-paced scenario - it makes sense to add a Note "If you were not using DDB table during some period of time - you will have spare capacity as burst - that's why you could go beyong 5 WCUs per second during the load".

[switch180]

Starting with Adv Design Patterns lab first and then rolling to the others:

• [x] Migrate Adv Design Patterns Public CFN template from EC2 to C9 instance
• [x] Update Adv Design Pattern doc pages for external setup to mention the new C9 method
• [x] Updates Adv Design Pattern guide's "code review" sections to mention C9 (and try to avoid screenshots bc they will get stale eventually)
• [x] Update internal CFN template to use C9 instance, then update internal documentation on lab

[switch180]

All work done. Resolving.