Extend EveBootOrderLib to read the opt/eve.bootorder fw_cfg file, log
the boot options, and push USB entries forward or remove them depending
on the “usb”/“nousb” value. This patch adds the fw_cfg reader,
prioritization logic, and the necessary UefiLib dependency so future
firmware builds can respond to the boot-order hints.

Signed-off-by: Nikolay Martyanov <nikolay@zededa.com>

Introduce boot order plumbing in Pillar types so VMs can apply a
consistent boot device priority and report where it came from.

This adds a BootOrder field to VmConfig and defines a new global setting
(app.boot.order) with validation for supported values. It also extends
AppInstanceConfig to keep the controller-provided boot order alongside
the effective value and track the selected source, and introduces
LPS-facing structs to cache per-app boot config and publish effective
boot order + source without triggering unnecessary domain restarts.

Signed-off-by: Nikolay Martyanov <nikolay@zededa.com>

Wire zedagent and localcommand together to let the Local Profile Server
override per-app VM boot order and keep the effective value consistent
across restarts and config refreshes.

This adds a small boot order resolver that applies precedence (LPS over
controller over device property) and stores the raw controller value so
the effective boot order can be re-evaluated when LPS clears an override
or app.boot.order changes. Boot order source is tracked alongside the
effective setting for LPS reporting.

Localcommand gains a dedicated /api/v1/appbootinfo task that
periodically posts the effective boot order and processes any boot
config returned by LPS, with persistence to disk, cache-based change
detection, and throttling behavior when LPS indicates the feature is not
configured. A mutex guards the AppInstanceConfig publish
read-modify-write path since updates can now arrive from multiple
goroutines.

Signed-off-by: Nikolay Martyanov <nikolay@zededa.com>

Enable VM boot device prioritization by exporting the resolved boot
order into the QEMU config as an OVMF-readable fw_cfg entry.

This maps the BootOrder enum to the string values expected by
EveBootOrderLib and injects opt/eve.bootorder only for FML/OVMF guests
(skipping the virt machine type). Unit tests cover USB and NoUSB
settings, absence of the section when unset, and the ARM/virt exclusion.

Signed-off-by: Nikolay Martyanov <nikolay@zededa.com>

Handle boot order updates as a special-case FixedResources change so
users get a clear, non-fatal indication that a restart is needed to
apply the new setting.

When the diff between configs shows that only FixedResources.BootOrder
changed, zedmanager now records a warning-level status message instead
of failing the modify path for missing restart commands. Other
FixedResources changes keep the existing stricter behavior and still
require an explicit restart request.

Signed-off-by: Nikolay Martyanov <nikolay@zededa.com>