feat(rom): Add ECDSA and MLDSA verify commands (#2285)This commit adds support for the ECDSA384_VERIFY mailbox command in ROM,including:- New verify module in common crate with ECDSA verification  implementation- Test cases for valid and invalid signaturesAdded helper methods to MldsaVerifyReq for safely extracting fields fromraw byte slices. This makes it possible to decode a variable sized inputwithout mapping the whole MAX_LEN struct with zerocopy (be it on thestack or in unused mailbox SRAM).Simplified MldsaVerifyCmd to use these new helpers instead of manualunsafe mailbox access. Removed MailboxRawAccess trait since it's nolonger needed.

Increase disk size when using VCK190 tools (#2300)

feat(crypto): Add zeroize support for Aes and Mldsa87 (#2296)This commit adds zeroize functionality for Aes and Mldsa87 cryptographicblocks in the error handler. The changes ensure sensitive cryptographicdata is properly cleared during fatal error handling scenarios. Thezeroize methods are marked as unsafe since they must only be called whenpending operations won't be used afterward.

feat(crypto): Add zeroize support for Aes and Mldsa87 (#2296)This commit adds zeroize functionality for Aes and Mldsa87 cryptographicblocks in the error handler. The changes ensure sensitive cryptographicdata is properly cleared during fatal error handling scenarios. Thezeroize methods are marked as unsafe since they must only be called whenpending operations won't be used afterward.

Add instructions for FPGA Host Runner (#2236)* Add instructions for FPGA Host Runner* Apply suggestions from code reviewCo-authored-by: Zach Halvorsen <zhalvorsen@google.com>---------Co-authored-by: Zach Halvorsen <zhalvorsen@google.com>

Add instructions for FPGA Host Runner (#2236)* Add instructions for FPGA Host Runner* Apply suggestions from code reviewCo-authored-by: Zach Halvorsen <zhalvorsen@google.com>---------Co-authored-by: Zach Halvorsen <zhalvorsen@google.com>

Add instructions for FPGA Host Runner (#2236)* Add instructions for FPGA Host Runner* Apply suggestions from code reviewCo-authored-by: Zach Halvorsen <zhalvorsen@google.com>---------Co-authored-by: Zach Halvorsen <zhalvorsen@google.com>

Add a mapping between Firmware Image ID to EXEC/GO Bit (#2281)* Add a mapping between Firmware Image ID to the EXEC/GO BitImplement mapping between a specific image to its corresponding EXEC/GoBit in the SOC Manifest.Added an 8-bit field within the 'flags' field in the Image Metadataentry that will map to the exec bit for the image.This will be used when determining which EXEC/GO bit will be set duringfirmware activation when executing the ACTIVATE firmware command.* Addressed feedbackUse only 7 bits for exec/go bit field in manifest* Add comment on on reserved bits for exec bit

Add a mapping between Firmware Image ID to EXEC/GO Bit (#2281)* Add a mapping between Firmware Image ID to the EXEC/GO BitImplement mapping between a specific image to its corresponding EXEC/GoBit in the SOC Manifest.Added an 8-bit field within the 'flags' field in the Image Metadataentry that will map to the exec bit for the image.This will be used when determining which EXEC/GO bit will be set duringfirmware activation when executing the ACTIVATE firmware command.* Addressed feedbackUse only 7 bits for exec/go bit field in manifest* Add comment on on reserved bits for exec bit

Add a mapping between Firmware Image ID to EXEC/GO Bit (#2281)* Add a mapping between Firmware Image ID to the EXEC/GO BitImplement mapping between a specific image to its corresponding EXEC/GoBit in the SOC Manifest.Added an 8-bit field within the 'flags' field in the Image Metadataentry that will map to the exec bit for the image.This will be used when determining which EXEC/GO bit will be set duringfirmware activation when executing the ACTIVATE firmware command.* Addressed feedbackUse only 7 bits for exec/go bit field in manifest* Add comment on on reserved bits for exec bit