Ability to specify CDROM drive (or any IDE drive) as a secondary drive in an IDE chain

When adding a drive representing an IDE CDROM, it seems to always appear as the primary disk on the secondary IDE controller.

I have a preconfigured VM that expects to find the CDROM drive as the secondary drive in the primary IDE controller, and I'm looking for the option to specify an ATAPI/IDE CDROM drive with address 0:1, the equivalent of this:

`-drive if=ide,index=1,media=cdrom`

Adding the above to the additional QEMU arguments works, to the extent that the drive is recognized by the guest OS. However, with this arrangement, UTM does not allow me to select a CDROM image file from the UI, and specifying a file in the option above using `file=` fails _(even if the file is located within the app's sandbox container)_ presumably due to #2483.

When adding a Drive, it would be nice to have an option to select the drive address. For example, in 86Box you have the choice of "0:0" or "0:1" with IDE, and additional options for SCSI-ID when working with SCSI drives.

For now, I can work around this as follows:

1. Add Floppy drive to system.
2. Configure Serial port as QEMU monitor using built-in terminal.
3. Select the desired CDROM image `` as the floppy drive image, in order to bypass sandbox.
4. In QEMU monitor, run `change ide0-cd1 `

_Note: I'm using UTM Version 4.1.6 (75)_