Need ability to ignore/no-verify SSL for proxy support.

**Describe the bug**
While going through a company proxy, the CLI tool breaks. In order to for it to BEGIN working, I had to manually make the changes present in issue #459 and PR #869 . Is there any update on pulling those changes in?

Completing those changes manually allowed me to succesfully run the `amplify init` command.

Though when trying to push/publish resources, I get a self-signed cert error.

My thought's on a fix would be to allow a --no-verify-ssl type flag to ignore/allow self-signed certs as they can be common with company proxies.

**To Reproduce**
Steps to reproduce the behavior:
1. Install the CLI tool like normal
2. Run through the manual changes for #459 & #869
3. Be behind company proxy
4. Run `amplify init `for a project
5. Notice bootstrap and preliminary resources are made.
6. Add a few resources in
7. Try to push/publish

**Expected behavior**
Resources are provisioned correctly and I get a $50,000 raise.

**Screenshots**

This is what trying to push/publish produces:

`2019-05-13T15:31:29.112Z - error: uncaughtException: self signed certificate in certificate chain
`
**Desktop (please complete the following information):**
- OS: Windows 10
- Browser [e.g. chrome, safari]
- Amplify version: 1.6.4

**Additional context**

I am behind a company proxy with a self-signed cert.