Allow ZMQ protocol specifying in HTTP server segregated by protocol vs. instance name mapping instead of a list of instance names

[VigneshVSV]

Mostly, the HTTP server will be used in INPROC transport with Thing's ZMQ server - this means one hardware per process. Here ZMQ will work as a thread coordinator & scheduler, like a threading.Lock() object.

Nevertheless, for certain cases, people may want to use IPC with HTTP server or TCP communication with HTTP server for a hardware running in some other computer. Although support already exists for this from ZMQ side, it has not been added to HTTPServer's init

Possible steps -

• Define how the first argument things has to be specified by the user, right now its a list with instance names and assumes IPC (which is again contradictory with the first statement of this issue) - it may be a dict of lists or whatever
• edit HTTPServer.update_router_with_thing or zmq_client_pool to account the correct ZMQ protocol for each thing
• edit Thing's own run_with_http_server method to account for INPROC correctly after making the changes