add initial integration tests for websocket client

[hoanhan101]

This PR:

• make integration tests for http and websocket client run separately
• update websocket latest scheme
• add initial integration tests for websocket (add integration tests #63)

Note that some of these tests are commented because of 500 response from server.

[edaniszewski]

Left a question, but largely looks good.

The 500 responses from Synse Server are interesting. Are you able to get the logs from Synse Server for those errors? Or just a dump of all logs from Synse Server for the test run? It could be helpful to figure out whats going on. I think some of them might be related to unexpected input data, but even if it is an issue with how the client is preparing the data, I think Synse Server could have improved error responses to more clearly indicate that.

[edaniszewski]

Why do we run the http and websocket integration tests separately? I'm sure there's a reason, just wanted to know

[hoanhan101]

We have a custom config for the emulator plugin to run the tests against. If we let the http and websocket integration tests run together, the http ones would go first and modify the config. Once the websocket ones run, we have to run the tests upon the modified config. It's confusing sometimes. So basically, letting them run separately makes sure that they are independent of each other and alway have a fresh start.