Add WithSecureBootPolicyProfile quirk for devices that measure secure boot policy to other PCRs

We have encountered a device that measures the `EV_EFI_VARIABLE_AUTHORITY` secure boot verification event for a UEFI driver that's not part of the platform firmware to PCR2. Whilst PCR2 is meant to be used to measure code that is executed outside of the platform firmware (eg, for PE images, measuring their Authenticode digest with the `EV_EFI_BOOT_SERVICES_DRIVER` or `EV_EFI_RUNTIME_SERVICES_DRIVER` event types), secure boot policy - which includes secure boot configuration (`EV_EFI_VARIABLE_DRIVER_CONFIG` event types) and secure boot verification events to indicate which CAs have been used to authenticate code (`EV_EFI_VARIABLE_AUTHORITY` event types) - should only be measured to PCR7.

In this case we have encountered, PCR7 is not useful on its own for determining secure boot policy - we will need a quirk to detect this case and make PCR2 a companion of PCR7 (ie, if PCR7 is included in the profile then PCR2 must also be included in order to seal keys against a device's secure boot policy).

Note that this will be working around a genuine firmware implementation bug.