Describe the bug
Following the new release which includes #1829 I am running into an issue when cloning a VM that has 2 disks (boot and efi) where we move the boot disk to another datastore.

In the TF_LOG I see it moves the boot disk to the correct datastore, but then continues to use its old id when setting the final bits.

tf_http_req_body="virtio0=file%3Dshared-ssd%3Avm-108-disk-1%2Csize%3D8589934592%2Caio%3Dio_uring%2Cbackup%3D0%2Ciothread%3D1%2Cdiscard%3Dignore%2Ccache%3Dnone%2Creplicate%3D1"

To Reproduce
Steps to reproduce the behavior:

Have a VM Template with 2 disks, boot and efi, both on the same datastore.

Clone a VM from it, while setting the boot disk to be on another datastore.

See the error:

2025-03-25T13:43:38.406+0100 [ERROR] provider.terraform-provider-proxmox_v0.73.2: Response contains error diagnostic: @caller=/home/runner/go/pkg/mod/github.com/hashicorp/terraform-plugin-go@v0.26.0/tfprotov6/internal/diag/diagnostics.go:58 tf_req_id=672dc621-5785-b340-2ed2-68faabea6640 tf_rpc=ApplyResourceChange tf_provider_addr=registry.terraform.io/bpg/proxmox @module=sdk.proto diagnostic_detail="" diagnostic_severity=ERROR diagnostic_summary="disk update fails: error updating VM: received an HTTP 500 response - Reason: Internal Server Error" tf_proto_version=6.8 tf_resource_type=proxmox_virtual_environment_vm timestamp="2025-03-25T13:43:38.406+0100"

Expected behavior
It should use the correct id to set the disk attributes.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

• Single or clustered Proxmox:
• Proxmox version:
• Provider version (ideally it should be the latest version):
• Terraform/OpenTofu version:
• OS (where you run Terraform/OpenTofu from):
• Debug logs (TF_LOG=DEBUG terraform apply):