Devoncarew new apis

Add support for the new `chrome.sockets` API.

The main issue I ran into is that the new sockets API defines different classes, with the same names, as the existing `chrome.socket` API. So, `CreateInfo` in both libraries, but they are semantically different classes. Not awesome.

I choose to rename the existing socket classes to avoid the conflict. This is with the idea that the new API is better, and the old API is probably on its way to being deprecated. I could easily be convinced to rename the new classes, and avoid breaking existing users of the library. Not sure which is better.

@financeCoding 

Also, Adam, can you turn on running drone.io tests for each branch? I'd like to get this tests on the bot before merging into master. Thanks!