Option to Generate a Unique client ID Based on Hardware ID

When installing a custom RustDesk client on a PC, it correctly generates a unique "RustDesk ID" and registers the PC on the RustDesk Pro website. However, if I create an image of this PC and clone it onto another machine, the RustDesk ID remains the same besides the hardware ID changed.

Expected Behavior
Each cloned PC should receive a new RustDesk ID based on its unique hardware, similar to how TeamViewer handles client IDs.

Current Behavior
Currently, after cloning a master image, all new PCs retain the same RustDesk Client ID as the original system. This requires manually reinstalling RustDesk after imaging to ensure each device gets a unique ID.

Proposed Solution
Introduce an option in the RustDesk client configuration to bind the ID generation to a hardware identifier, such as:

bind_to_hardware_id = Y # Default: N

When enabled, RustDesk would generate a new ID based on the unique hardware fingerprint of the machine, preventing duplicate IDs across cloned systems.

Use Case
This would be particularly helpful in environments where multiple PCs are deployed from a master image, ensuring each receives a unique RustDesk ID without requiring manual reinstallation.

Additional Context
This issue impacts IT admins who manage multiple deployments using imaging techniques.
Other remote support solutions like TeamViewer already provide a similar mechanism to prevent duplicate IDs.

No files, tests, or entry points are named. Start by locating the client ID generation and configuration handling, then investigate how cloned installations retain IDs and which hardware identifier can be used. Done means an opt-in setting gives cloned PCs distinct IDs without requiring reinstallation.