Implement qube migration between storage pools

[fepitre]

The problem you're addressing (if any)

Currently, in Qubes OS, there is no built-in option for migrating a qube from one pool to another. The workaround involves renaming the qube with a prefix, cloning it to the desired pool, and then deleting the original qube. However, this approach can lead to issues, especially when the qube serves as a templatevm for other qubes, as properties may not follow the renamed qube.

The solution you'd like

Introduce a feature that allows users to migrate qubes between storage pools seamlessly within the Qubes Manager or via command-line tools. This feature should handle property transfer and ensure that any dependent qubes, such as those using the migrated qube as a templatevm, audiovm and so on, remain unaffected by the migration.

The value to a user, and who that user might be

• Streamlined Workflow: Users who need to manage their qubes across different storage pools will benefit from this enhancement, as it provides a more straightforward and efficient method for migrating qubes.
• Reduced Risk of Errors: Implementing a dedicated migration feature will reduce the likelihood of user errors and potential issues that may arise from manual renaming, cloning, and deletion procedures.
• Improved Maintenance: System administrators and power users responsible for managing multiple qubes and storage resources will find this feature valuable for maintaining their Qubes OS environments effectively.

Completion criteria checklist

• Design and implement a user-friendly interface or command-line tool for migrating qubes between storage pools.
• Update documentation and user guides to include instructions on utilizing the new qube migration functionality.