Merge lp://staging/~xnox/debian-cd/ubuntu-fwsetup into lp://staging/~ubuntu-cdimage/debian-cd/ubun3

What's the rationale for a firmware setup menu entry? On installed systems, we offer this because if UEFI fastboot is enabled it may be the only way to select a non-default boot option. But how would a system with UEFI fastboot have ever booted the installer image in the first place? And, having booted it, why would the user need a system setup menu option, instead of either a) proceeding to install, or b) removing the installer from the system and rebooting?

The delay on EDK2 / OVMF builds to enter setup mode is too short, because it takes a while for SPICE to connect the keyabord. So I need it on VMs to enter setup when doing iso testing.

It's not unrealistic for people to miss the window when one can enter bios on real hardware by default. As one has to do it whilst the screen is completely black. I.e. on my dell laptop I choose to add a 30s boot delay in bios settings, as the window to enter bios settings was too short for me.

Steve, updated. Please re-review.

ok, I was -1 on the idea of using fwsetup as a replacement for the "Boot next device" option, but I can see that the rationale for having this on installed systems also applies equally well to live images (even though in practice it would be unusual for a system to both be configured with UEFI fastboot and have the live image as the first boot option that you can't remove). So I'm +1 on adding both of these.