Move appropriate @types back to dependencies

[sheldonkwok]

The types seem to have drifted back into the devDependencies from when I moved them over originally in #39
Reasoning: microsoft/types-publisher#81 (comment)
I'm happy to rebase after related pull requests go through.

Related:
#156
#160
#200
#201

[brendandburns]

@sheldonkwok this generally looks good, but we're removing bluebird b/c it breaks es6 users.

[sheldonkwok]

No problem, I can rebase after that one is merged or do it here if you want

[sheldonkwok]

Rebased

[drubin]

/lgtm

I have been wondering if it's worth adding a note to the readme about where to put @types definitions. It seems we have gone back and forth between devDeps and Deps a few times in the last few months.

What do you think maybe a simple metric like any return value from a public function needs to be in deps else they should go into devdeps

[sheldonkwok]

That sounds good but it might be harder to keep track of if things get pretty nested. An easy way might just be: Every dep should have its @types also be in the dep.

[brendandburns]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brendandburns, sheldonkwok

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [brendandburns]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment