Floodlight's Static Flow Pusher REST interface expects "posted data"
for DELETE requests. It uses this posted data to identify which entry
should be deleted. However, the RFC 2616 states that resources
to be deleted using the DELETE method should be identified by a
URI (not by posted data):
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.7

This is a problem when you try to use a spec-compliant framework to
communicate with the REST interface provided by StaticFlowEntryPusher
module. The Restlet framework, that is being used in the implementation
of the module itself, is an example. It prevents you from posting data with
a DELETE method, according to what is specified in the HTTP1.1 RFC.

    1) Ability to ask for last N events
    2) Events now show up with most-recent-first
    3) Including ThreadName as one of the columns
    4) Ensuring moduleName and eventNames in URL do not include '/'
    5) Removing dead code in Event.java
    6) Updating unit tests

accomodating the CLI)

change flow mod event names to being delimited by "-"

as the left-most columns

o show openflow cluster count with/without tunnels
o show external port count for each external cluster

1) new event for BVS Interface(s) assigned
2) new EventFieldTypes for LIST_OBJECT, SREF_OBJECT and SREF_LIST_OBJECT
3) removing LIST_VLAN from EventFieldType as it is superseded by LIST_OBJECT

[BVS-420] Add unit tests for checking if device moved notifications are sent or not under certain situations.

The previous fix is not correct.  The fix generates a device moved event when the attachment points are not even updated.

Revert "Device moved notification has to be generated when the new attachment point was already in the oldAP list."

This reverts commit 2d6a75c4116790db7d1ddaa53e0d6d873d035815.

or explicitly ingore it if it's safe