Comment 9 for bug 1785332

I am informed that grub now automatically delays boot if it cannot write to /boot (which avoids the issue where you put /boot on raid and then install a bad kernel, and then can't fix your machine because grub can't record the failed boot and interrupting the bootloader is hard over ipmi or in UEFI boot or whatever) so, subject to testing that this is correct, we can just lift the restriction. We should still leave some of the code paths present though because support for encrypted LVM will land soon and we don't want to let the user have /boot on that...