Tidy up topology and get rid of some many redundant functions in ITopologyService. Also, fix a bug that prevents outgoing broadcast ports from being queried on single-switch islands.

Integrated new topology code and updated unit tests to a passing state. I'd be more comfortable adding more unit tests to the topology. Also made some changes to the link discovery manager's latency subsystem. We start with a baseline latency based on the switch's features reply turnaround time. This should be relatively quick -- just like an echo. Next step for latency is to keep a rolling list of past latencies for more defined topology updates based on latency updates. We don't want to update latencies too frequently, since tiny changes (or outliers) shouldn't require a complete topology recomputation.

First round of support for primitive link latency detection. We do not presently account for the latency between the switches and the controller.

This reverts commit 4ae94669.

Refactored structure of core components to work with openflowj-loxi.
Presently refactoring Routing, Firewall, Forwarding, DeviceManager,
LinkDiscovery, Topology, and LearningSwitch.
Hub has been refactored.

Topolgoy: don't remove ports the collection returned by the switch.  Make BVS port names case-insensitive

Change topologyChanged() method signature to provide an unmodifiable list of applied updates during the method call.

Add an interface method to ITopologyService to get all the switches in the same openflow domain as a given switch id.

Introducing rate control in sending BDDP messages, quarantining ports as they join the network, change API getEnabledPorts().

Updates to attachment point learning and udpating.  DeviceManager listens to topologyChanged() events.  Whenever a port goes down or a switch is removed, attachment points are updated.  Cleanup of link discovery manager updates; cleanup also includes port up/down switch update/removed messages.

BSC-2116

topology keeps a list of applied link updates. topologyAware modules can query updated links after getting topologyChanged event

DeviceManager update to take into account that previous attachment belongs to non-broadcast domain attachment point.
Adding an interface to ITopologyService that indicates if tunnels are enabled for traffic between two hosts.

2 - Update module HA role change actions
3 - Add unit tests for HA role changes

Introduce a convenience method inSameIsland, which is the same as inSameCluster.  In future, they may have different functionalities.

Introduce a method called isConsistent(..) that compares an old attachment and a new attachment point. If the new attachment point is not consistent with the old one, then it has to be learnt by the device manager.

(1) Device manager will drop packets (as the first step) if the topology indicates the packet-in port is not allowed for incoming transmissions. (2) Remove a log message from LinkDiscoveryManager. (3) Topology provides a service called isAllowed() that indicates if the port is enabled for incoming and outgoing traffic.  (4) Tests are modified accordingly.

Device manager will learn new attachment points only if the switch ports do not belong to the same broadcast domain.

Fixed JUnit tests.