efi/preinstall, efi: ensure WithBootManagerCodeProfile handles the installer being launched from the firmware settings UI

If the installer is launched from the firmware settings UI, PCR4 contains the corresponding load events in the pre-OS environment. Because we just assume that these are system preparation applications, they get copied to the initial profile during install. This causes the subsequent post-install boot to fail to unlock because the firmware settings UI isn't loaded and its events are thus not measured.

We should exclude pre-OS load events that don't match to a corresponding `SysPrepXXXX` variable, and which aren't related to Absolute, as some devices correctly load and measure Absolute as part of the pre-OS environment - Dell devices get this wrong by loading and measuring it as part of the OS-present environment, for which we already have a workaround.