Add a separate interface for displaying all requests/responses between the controller and the drones.

[ba11b0y]

This issue extends #137 in the hydrus repository.

To allow the user to get a peek under the hood and understand how the drones communicate with the central controller dynamically, the UI should also contain an interface which displays the whole request/response communication between the drones and the controller, containing columns namely Drone ID, Request Method, URI, Status code of Response, Body of Response

[ba11b0y]

Since both this issue and #22 would involve major UI changes, should I include both of these features in different HTML files and not touch the main UI or something else?
My suggestion would be to move HttpApiLogs, Controller Logs, Drone Logs and Drone Datastream somewhere else(maybe under a Logs section) considering their relative importance on the main GUI when compared to the request/response b/w drones and the central controller.
Also a Bootstrap modal(with a save button ofcourse) for editing the vocabulary.

@Mec-iS @xadahiya Any ideas for the new restructuring?

[Mec-iS]

We need further investigation about, but this could be implemented with #25