- When computing uptimes and start times use the information provided by the JVM.

Conflicts:
	floodlight/src/main/java/net/floodlightcontroller/core/internal/Controller.java

from null to non-null as device moved

[BSC-3247] DeviceManager must learn devices correctly when the ethernet destination MAC in an ARP response is different from sender hardware address.  A device corresponding to the sender hardware address and sender protocol address needs to be learned.  Update unit tests accordingly.

[BVS-324] Remove the usage of getAPMap() when retrieving attachmentpoints.  Its use is needed only when computing duplicates.

findbugs stuff (https://github.com/bigswitch/bigswitchcontroller/pull/2616)

NodePortTuple class implements comparable to allow for sorting of nodeport tuples. The sorting is first based on the switch id and then on the port id.

BSC-3210 - floodlight was writing a controller node into cassandra, this is incorrect. So, if the properties file does not contain controller-id set, then floodlight will write localhost, which is causing a third controller node is cassandra. also there is no need for first boot and upgrade to write controller-id into properties files. so cleaning these up.

Need to run "ant eclipse" to get the new settings.

When creating the eclipse project files we also create a project
specific config for FindBugs that sets the exclude file correctly.