grubby shows the kernel image and initramfs are installed to /boot/boot but they are actually installed to /boot/
```
# testing-farm reserve --compose Fedora-44 --arch aarch64

# grubby --info=DEFAULT
index=0
kernel="/boot/boot/vmlinuz-6.19.10-300.fc44.aarch64"
args="no_timer_check console=tty1 console=ttyAMA0,115200n8 systemd.firstboot=off rootflags=subvol=root"
root="UUID=f7895286-af40-4b76-b759-a6c61d4de657"
initrd="/boot/boot/initramfs-6.19.10-300.fc44.aarch64.img"

# grubby --info=/boot/boot/vmlinuz-6.19.10-300.fc44.aarch64
The param /boot/boot/vmlinuz-6.19.10-300.fc44.aarch64 is incorrect

# ls /boot/vmlinuz-6.19.10-300.fc44.aarch64 
/boot/vmlinuz-6.19.10-300.fc44.aarch64
```

This also happens to x86_64,
```
# testing-farm reserve --compose Fedora-44 --arch x86_64

# grubby --info=DEFAULT
index=1
kernel="/boot/boot/vmlinuz-7.0.8-200.fc44.x86_64"
args="ro rootflags=subvol=root no_timer_check console=tty1 console=ttyS0,115200n8 systemd.firstboot=off rootflags=subvol=root"
root="UUID=bacc1708-7577-412b-83c8-5e12a83da84b"
initrd="/boot/boot/initramfs-7.0.8-200.fc44.x86_64.img"
title="Fedora Linux (7.0.8-200.fc44.x86_64) 44 (Cloud Edition)"
id="ec29864d34ea04fc0b1e1abcb7a647c3-7.0.8-200.fc44.x86_64"
```

This issue can also be reproduced on locally downloaded Fedora-Cloud-Base-Generic-44-1.7.x86_64.qcow2.

Impact
======

Tools e.g. [1][2] that parse grubby --info output and use the kernel= value to locate the kernel file on the running system will fail.

[1] https://github.com/rhkdump/kernel-auto-bisect/
[2] https://github.com/rhkdump/kdump-utils




Reproducible: Always