NCLController accepts SDNNetworkFlow as parameter in allocateFlow().

NCLController API and implementation has changed in order to use SDNNetworkFlows instead of FlowRequests.
- Logic for Tranlating from FlowRequest to SDNNetworkFlow has been moved to a dedicated component (RequestToFlowLogic) that is part of the provisioner.
- Logic for creating Flow from already allocated SDNNetworkFlow(s) has been moved to NCLProvisioner.
- NCLController is now very similar to SDNNetwork IOFProvisioningNetworkCapability.

Some tests have been updated.

This patch fixes issue:
http://jira.i2cat.net:8080/browse/OPENNAAS-1182
Merge pull request #739 from isartcanyameres/feature/allocate-most-specific-flow

NCLController accepts SDNNetworkFlow as parameter in allocateFlow().