Adds Quantum Router Extension to Quantum REST Proxy Plugin

Addresses BVS-95

Unit tests have also been added. This patch leverages existing L3
Quantum mixin and unit tests. Changes had to made to disable floating
IPs and external network references.
Adding unit test cases to run against the dummy server. These do not include tests for the
router extension. Those will be added separately as a followup.

These tests are to be run as follows (from top level quantum directory):
./run_tests.sh quantum.plugins.bigswitch.tests.test_restproxy_plugin_with_server
Adding REST calls from plugin to Quantum App for create, update, and
delete router.

Also adding unit tests for testing with dummy server for these operations.

Also upgrading wire protocol version to v1.1.

Some request bodies may not be complete.
Adds implementation for add_router_interface and remove_router_interface
in plugin. Network ID is being sent as interface ID.
Adding more fields in the request body of add_router_interface.
Adding support for subnet create/update/delete (network update is sent).
Changing request body data such that all attributes of all resources
are well be sent in POST/PUT. Not all of these attributes will be used
on the controller side, but this makes the wire protocol consistent. This
is a superset of all the attributes being sent, so no attributes are being
dropped.

Also general cleanup and refactoring of repeated code.
Changing add_router_interface to a POST instead of PUT
Adding support for the sending the entire topology in the sync operation.

Also adding test case for the same.
BVS-98 - Adding support for Quantum Instance ID

Also fixing test server so that debug_env option can be used to test this.
Changing topology schema to send an array of networks and routers,
instead of a dictionary.

Also adding a test which validates the topology schema.

There are some pep8 errors on account of long lines which need to be fixed.
Changing HTTP header Quantum-ID to Instance-ID.
Changes to fix pep8 errors.

One pep8 error still remaining. This pep8 error is for the topology schema string.
More changes will be required to read this string from a file which will fix the
error.
When a resource does not have a state, an UP state is sent. Currently
this is in the case of the subnet.