Classifier reacts to first SF location updates

Classifier reacts to first SF location updates

Whenever the first SF in an RSP migrates to another compute node, the
classifier rules are updated accordingly - whether sending the packet
through a different tunnel connected to the new compute node, or, in
scenarios when the SF moved to the compute node where the classifier is
installed, by jumping directly to the SFC transport ingress table.

The helper methods on the OpenflowClassifierProcessor were moved into a
new class - ClassifierHandler.

The ClassifierRspUpdateDataGetter was finished, providing 2 methods:
  - filter all ACLs whose ACEs impact the supplied RSP
  - filter all ScfClassifier objects that implement those ACLs

The ClassifierRspsUpdateListener was added logic on how to identify the
movement of the first SF in any RSP, and also triggers the classifier
flows update through the ClassifierRspUpdateProcessor.

The ClassifierRspUpdateProcessor follows the same principle of the
OpenflowClassifierProcessor - build all the flows to be installed. A new
class was created to separate the concerns (classifier updates have the
RSP as its single argument, whereas classifier add/delete have the ACL
and the ScfClassifier objects as arguments).

Everything else are tests (+- 600 lines)

Change-Id: I487d98d282b28aefd79d0658fcc50e20897beffa
Signed-off-by: Miguel Duarte <miguel.duarte.de.mora.barroso@ericsson.com>