fix bind changed not handled to 1.1

[zhangxu19830126]

What type of PR is this?

• API-change
• BUG
• Improvement
• Documentation
• Feature
• Test and CI
• Code Refactoring

Which issue(s) this PR fixes:

issue #14241

What this PR does / why we need it:

fix bind changed not handled

[matrix-meow]

@zhangxu19830126 Thanks for your contributions!

Review:

Title: fix bind changed not handled to 1.1

Body: The pull request is a bug fix for issue #14241. It fixes an issue where bind changes were not being handled correctly.

Changes:

1. In pkg/lockservice/service_remote.go, the code has been modified to handle stale bind changes. The old bind lock table is now removed when a stale bind is found. This is done by calling the removeWithFilter method on the s.tables object.
2. In pkg/lockservice/service_remote_test.go, an assertion has been added to check if the lock table is nil after a bind change.
3. In pkg/pb/lock/lock.go, a new method Equal has been added to the LockTable struct. This method checks if two LockTable objects have the same table and version.

Overall, the changes in this pull request address the issue of stale bind changes not being handled correctly. The code modifications seem to be correct and should fix the problem. However, there are a few suggestions for improvement:

1. Security: It's important to ensure that the removal of the old bind lock table is done securely. This means verifying the identity of the requester before removing the table. Consider adding authentication or authorization checks to ensure that only authorized users can remove the table.

2. Code Optimization: The code in pkg/lockservice/service_remote.go can be optimized by using a more efficient data structure for storing the lock tables. Currently, the code iterates over all lock tables to find the one that needs to be removed. This can be slow if there are a large number of lock tables. Consider using a data structure like a map or a hash table to improve the lookup time.

3. Test Coverage: It would be beneficial to add more test cases to cover different scenarios and edge cases related to bind changes. This will help ensure that the code handles all possible scenarios correctly.

4. Documentation: It would be helpful to add comments or documentation explaining the purpose and behavior of the Equal method in pkg/pb/lock/lock.go. This will make it easier for other developers to understand and use the code.

Addressing these suggestions will help improve the security, performance, and maintainability of the codebase.