Bug 6146 - Some Flows not found in DeviceFlowRegistry

Bug 6146 - Some Flows not found in DeviceFlowRegistry

Hook in the custom comparator code from Helium design
that will bring in the custom flow-match constructs
comparison and address all the regression scenario
poped up because of the hashcode/equals based matching.
Default equals/hashcode approach won't work for flow matching,
because flows match contructs (e.g ip/mac) are not normalized
and also because of the extension augmentation.

This hook don't change the default behavior, it will trigger
only if the flow is not found in the flowRegistry, so as far
as user installs flow with the normalized values, custom
comparator is not required.

Change-Id: Ibeba9693d1c4dc0092fa9a11c8acd0ce7cf7a15d
Signed-off-by: Anil Vishnoi <vishnoianil@gmail.com>