fix(filelock): release replaced lock resources on move assignment

[89799969]

Closes #1934

Summary

• Release the destination lock resources before move assignment.
• Reuse the noexcept cleanup path from both the destructor and move assignment.
• Verify that the replaced lock path can be reopened immediately.

Validation

• git diff --check

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: 89799969

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[deepin-ci-robot]

Welcome @89799969! It looks like this is your first PR to OpenAtom-Linyaps/linyaps 🎉

[deepin-ci-robot]

Hi @89799969. Thanks for your PR.

I'm waiting for a OpenAtom-Linyaps member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[89799969]

Hi @dengbo11, could you please take a quick look and, if the patch is reasonable to test, add /ok-to-test so the remaining CI jobs can run?

This is a focused move-assignment resource cleanup fix for #1934. The license check, cppcheck, and pre-commit checks are already passing. Thanks!