controller: fix lsp not deleted in gc

[zhangzujian]

Pull Request

• Make sure you have followed Kube-OVN Code Style.

What type of this PR

Examples of user facing changes:

• Features
• Bug fixes
• Docs
• Tests

Which issue(s) this PR fixes

After upgrading kube-ovn to v1.14.6, some stale logical switch ports are not deleted in gc:

I0919 15:44:21.952382       7 gc.go:436] gc logical switch port acp-daemonset-m5wc5.e2eproject-acp-0-ns
I0919 15:47:24.083684       7 gc.go:436] gc logical switch port acp-daemonset-m5wc5.e2eproject-acp-0-ns
I0919 15:50:26.197093       7 gc.go:436] gc logical switch port acp-daemonset-m5wc5.e2eproject-acp-0-ns
I0919 15:53:28.168941       7 gc.go:436] gc logical switch port acp-daemonset-m5wc5.e2eproject-acp-0-ns
I0919 15:56:30.300947       7 gc.go:436] gc logical switch port acp-daemonset-m5wc5.e2eproject-acp-0-ns
I0919 15:59:32.394582       7 gc.go:436] gc logical switch port acp-daemonset-m5wc5.e2eproject-acp-0-ns
I0919 16:02:34.638748       7 gc.go:436] gc logical switch port acp-daemonset-m5wc5.e2eproject-acp-0-ns
I0919 16:05:36.632861       7 gc.go:436] gc logical switch port acp-daemonset-m5wc5.e2eproject-acp-0-ns
I0919 16:08:38.697615       7 gc.go:436] gc logical switch port acp-daemonset-m5wc5.e2eproject-acp-0-ns
...

It seems the libovsdb's Get() method does not return the logical switch port object and the deletion operation is skipped.

Currently I cannot figure not thre reason, so we need to avoid the problem by deleting logical switch ports by UUIDs.

[OneWithoutName]

升级到了1.14.15后，还是会出现残留的问题。

[zhangzujian]

@OneWithoutName StatefulSet 不要使用 force delete：https://kubernetes.io/zh-cn/docs/tasks/run-application/force-delete-stateful-set-pod/

[OneWithoutName]

@OneWithoutName StatefulSet 不要使用 force delete：https://kubernetes.io/zh-cn/docs/tasks/run-application/force-delete-stateful-set-pod/

核对了下，这个pod没有使用force delete，而是通过scale replicas的操作，类似3->0,0->3这样的

[OneWithoutName]

我弄错了，我以为这个PR是解决#5724 这个bug的。