Comment 4 for bug 2011536

> While f-k mostly generate files, I don't think flash-kernel is particularly good in the mode of "please ignore the current environment and generate artifacts for the following hardware target without flashing them to non-OS managed locations", perhaps it grew such support recently though. I would expect this to be done with something like FK_FORCE_TARGET_MACHINE or something, and then EFI/chroot/device-tree checks should be ignored and the machine db would be used, except for flashing to real hardware

I would say there is precedence for forcing installation/environments in flash-kernel with the use of FK_FORCE and FK_MACHINE, where you can override the VM/container and target machine detection.

I also wanted to add a new flag (FK_FORCE_EFI) rather than utilise the existing FK_FORCE flag so that the current behaviour doesn't change unexpectedly for users, in case someone is relying on this EFI detection.