VM couldn't be moved to "Data" when cloning it

> **BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.**

Quick searches for `clone`, `cloning`, `Data`, `moved`, and `couldn't` didn't help.

**Describe the issue**
I double-clicked a [downloaded](https://archive.org/details/windows-98-for-utm) UTM VM and it loaded as a shortcut. I attempted to clone the VM to import it into UTM with the rest of my VMs and received an error that the VM `clouldn't be moved to "Data".` Interestingly, it does appear the file was copied into UTM storage. When I click on a different VM and choose "Show in Finder" I see the VM I was trying to clone. Yet the VM does not appear in the app.

When I quit and reopen UTM, the VM is now listed, albeit with a UI bug of the list entry cut off. Scrolling the list allows it appear fully.

When trying to edit the settings of the cloned VM, I click the Save button and get the same error that the VM couldn't be moved to "Data." And I have to cancel my changes.

Comparing the cloned `config.plist` contents with a VM I recently created, I noticed the cloned VM's `ConfigurationVersion` is `2` while my VMs show that value as `4`. Is this perhaps an issue with UTM needing to migrate the VM configuration during cloning?

Thanks for making UTM open source and freely available!

**Configuration**
* UTM Version: 4.64, 4.6.5
* macOS Version: 15.4 (24E248)
* Mac Chip (Intel, M1, ...): M2 Max

**Crash log**

> If the app crashed, you need a crash log. To get your crash log, open Console.app, go to `Crash Reports`, and find the latest entry for either UTM, QEMU, QEMUHelper, or qemu-\*. Right click and choose `Reveal in Finder`. Attach the report here.

UTM does not crash.

**Debug log**

> For all issues related to running a VM, _including_ crashes, you should attach a debug log. (This is unavailable for macOS-on-macOS VMs. Attach an excerpt of your system log instead.)
To get the Debug log: open UTM, and open the settings for the VM you wish to launch. Near the top of the `QEMU` page is `Debug Log`. Turn it on and save the VM. After you experience the issue, open the VM settings again and select `Export Log...` and attach it here.

This is an issue when the VM is powered off so the steps described in the Issue template won't work. Also, I cannot save edits to the cloned VM as mentioned above.

**Upload VM**

> If your issue is related to a specific VM, please upload the config.plist from your VM's .utm directory. To get this, right-click the VM in UTM and choose "Show in Finder". Then right-click the selected file in Finder and choose "Show Package Contents". The config.plist file is now visible. Right-click it and choose "Compress". Attach the resulting config.plist.zip file here.
> You can upload the entire .utm if needed, but note this includes your VM's drive image and may contain personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

[config.plist.zip](https://github.com/user-attachments/files/19723280/config.plist.zip)