Fix so that operational store correctly removes protocol entries

Fix so that operational store correctly removes protocol entries

    Before, if a protocol entry was removed on ovsdb, we didn't
    remove it from the operational store.

    This is an artifact of using *merge* rather than *put*.
    Using merge is *still* a good idea for us, but what was happening
    was basically this.

    Say we got a report in the operational store of

    [protocol1, protocol1]

    which we dutifully merged.

    Then we got a report of
    [protocol2]

    when that is *merged*... the protocol1 entry is left dangling,
    because its a *merge*.  To compensate, we have to be *very*
    specific about wanting to remove protocol1.

Change-Id: I17f8b9b26cea4e894d74b534335dc55f0097d8c8
Signed-off-by: Ed Warnicke <eaw@cisco.com>