This issue is now automatically resolved by garuda-update version 4.10.2. We do this without doing any funky -Rdd stuff, so this is a safer way and will allow for a safe reboot even if the update process was unable to complete for another reason. (Since the removal command of linux-firmware will succeed, while the normal system update could be cancelled for another reason)
In short:
Run garuda-update as always. No further intervention is needed.