Enable pipeline to support efi boot on Qualcomm platforms

[yogeshlal]

Problem

• Current KernelCI rootfs/ramdisk boot flow is not sufficient to scale coverage on Qualcomm targets in kernelci-lab.
• Some test scenarios require a full flashable image flow (partitioned image + EFI boot artifacts).

Proposal

Adopt a flasher-image based boot path for Qualcomm EFI targets in pipeline.

• Use boot_method: efi for Qualcomm platform entries.
• Consume a prebuilt flash_image artifact from internal hosting.
• Use kernelci-core EFI runtime flow (config/runtime/boot/efi.jinja2) to prepare and flash boot artifacts.

Flasher image source

Flasher images are generated using Qualcomm’s meta-qcom project:
https://github.com/qualcomm-linux/meta-qcom

These generated images are hosted internally and consumed by Qualcomm kernelci-lab (off-grid environment).

Reproducibility

If developers want to reproduce the exact flash image externally, meta-qcom README already documents the image generation steps.

Why this matters

This unlocks broader test coverage on Qualcomm hardware where ramdisk-only workflows are not representative of real boot/flash behavior.

PR list:
kernelci-core : kernelci/kernelci-core#3092
kernelci-pipeline : #1481