_delete_port_security_group_bindings not needed in ML2 delete_port

[Xurong Yang]

_delete_port_security_group_bindings will delete SecurityGroupPortBinding associated with the port being deleted. But since SecurityGroupPortBinding has a foreign key constraint with port and cascade deleting is defined, SecurityGroupPortBinding can be deleted when port is deleted, thus _delete_port_security_group_bindings call in ML2 delete_port is not needed and can be removed.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/124657

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/124657
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=87a3d9fc3a41e45d7c14517243b3f8bda9c0d367
Submitter: Jenkins
Branch: master

commit 87a3d9fc3a41e45d7c14517243b3f8bda9c0d367
Author: yangxurong <email address hidden>
Date: Mon Sep 29 11:37:19 2014 +0800

    Remove _delete_port_security_group_bindings from delete_port

    Since SecurityGroupPortBinding has a foreign key constraint with Port
    and cascade deleting is defined, SecurityGroupPortBinding can be
    deleted when port is deleted, thus _delete_port_security_group_bindings
    call in ML2 delete_port is not needed and can be removed. Redundant
    calls in other core plugins are also removed in this patch.

    _delete_port_security_group_bindings is needed when updating ports so
    this method cannot be removed directly.

    Change-Id: I33c787fbed46d6049d3b24ccd246a8484d8aa306
    Closes-Bug: #1373199