local controller - delete ports by cookie id

As a first step in this bug, a unified way to handle cookies is necessary. Otherwise, if two applications use the same cookie id for different purposes, l3 deleting by lport id might delete another app's flows which happens to use the same cookie bits and lport id for something else entirely.

Related fix proposed to branch: master
Review: https://review.openstack.org/428056

Reviewed: https://review.openstack.org/427261
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=5f07d7019c42f1b1c1801dc93206ef30b7d21691
Submitter: Jenkins
Branch: master

commit 5f07d7019c42f1b1c1801dc93206ef30b7d21691
Author: Omer Anson <email address hidden>
Date: Mon Jan 30 22:36:04 2017 +0200

    Add cookie infrastructure to Dragonflow

    Add a cookie infrastructure that allows global and local cookies to be
    allocated dynamically in dragonflow.

    Global cookies are cross-system. (e.g. l3 and security groups use these
    bits for the same thing)

    Local cookie space can be reused by applications (e.g. l3 and security
    groups can use the same bits for different things)

    Change-Id: I0e2dcc24ead244762cb5e9f3c18ad5f48652f914
    Related-Bug: #1471552

Reviewed: https://review.openstack.org/427612
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=ea64044851d04ff4ebabb36a37c16d8b5d3b2aaf
Submitter: Jenkins
Branch: master

commit ea64044851d04ff4ebabb36a37c16d8b5d3b2aaf
Author: Omer Anson <email address hidden>
Date: Wed Feb 1 11:46:53 2017 +0200

    Create an automatic cookie update mechanism

    Create a mechanism to automatically update the cookie value of flows.
    Specifically for global cookie bits (local cookie bits are the
    application's responsibility)

    Change-Id: I8483eae33c6c019413241c58fbf435d02d893750
    Related-Bug: #1471552

Reviewed: https://review.openstack.org/428056
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=afc50c8186e59934612c16e437adfc5b6777672b
Submitter: Jenkins
Branch: master

commit afc50c8186e59934612c16e437adfc5b6777672b
Author: Omer Anson <email address hidden>
Date: Wed Feb 1 13:08:34 2017 +0200

    Refactor Aging application

    As part of the work on cookies throughout Dragonflow, it was decided
    that this application would benefit from moving cookie information to be
    private, rather than sit in an external utility module.

    Additionally, the code used to connect to the OVS was made available to
    all applications via the shared base class.

    Lastly, ryu's openflow service necessary for synchronous communication
    was moved to df-local-controller.

    Change-Id: Ia52f3e49b077090fb6d6264628a10bc4af93c664
    Related-Bug: #1471552