fix(initrd): pad each chained initrd to a 4-byte boundary

Chained initrds were concatenated back to back. Linux only finds a cpio
archive at a 4-byte aligned offset when it unpacks concatenated
initrds, so a compressed initramfs with an odd length followed by
another archive, like a microcode or overlay cpio, failed to unpack.
Pad each initrd with zeros to a 4-byte boundary, as GRUB and
systemd-boot do.

crates/boot/src/actions/edera.rs

@@ -5,7 +5,7 @@ use alloc::{format, vec};
 use anyhow::{Context, Result, bail};
 use edera_sprout_config::actions::chainload::ChainloadConfiguration;
 use edera_sprout_config::actions::edera::EderaConfiguration;
-use edera_sprout_parsing::{build_xen_config, combine_options, empty_is_none};
+use edera_sprout_parsing::{append_initrd, build_xen_config, combine_options, empty_is_none};
 use eficore::media_loader::{
     MediaLoaderHandle,
     constants::xen::{
@@ -94,7 +94,10 @@ pub fn edera(context: Rc<SproutContext>, configuration: &EderaConfiguration) ->
         .chain(configuration.initrd_chain.iter())
     {
         if let Some(p) = empty_is_none(Some(p)) {
-            initrd_bytes.extend(read_loader_payload(&context, "initrd", p)?);
+            append_initrd(
+                &mut initrd_bytes,
+                &read_loader_payload(&context, "initrd", p)?,
+            );
         }
     }
     PlatformTpm::log_event(