Implement Client-Side Resource Unregistration

[YongGoose]

Check Ahead

• I have searched the issues of this repository and believe that this is not a duplicate.

• I am willing to try to implement this feature myself.

Why you need it?

This task focuses on implementing robust resource unregistration logic within the RMClient to properly manage the lifecycle of resources.

How it could be?

• Add destroy interface: Implement a destroy method that accepts resource information. This method should construct an UnregisterRMRequest and send it to the server to unregister the specific resource.

• Add destroyAll interface: Implement a destroyAll method to proactively notify the server that the client node is going offline. This is crucial for proper cleanup and state management on the server side.

• Conditional Unregistration: Before sending an UnregisterRMRequest, check the cached server version (from Issue 1). If the version is lower than 2.6.0, log a warning message indicating that UnregisterRMRequest is not supported by older server versions and therefore, resources cannot be unregistered.

Other related information

No response