Fix build-boot-artifacts-x86-host-sa and build-boot-artifacts-bfb-sa stages

[shevchenko-evgeny]

Description

Fix build process described in the installation guide.
This PR fixes issues in the build process, specifically related to boot artifacts preparation.

Type of Change

• Add - New feature or capability
• Change - Changes in existing functionality
• Fix - Bug fixes
• Remove - Removed features or deprecated functionality
• Internal - Internal changes (refactoring, tests, docs, etc.)

Related Issues (Optional)

Breaking Changes

• This PR contains breaking changes

Testing

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• No testing required (docs, internal refactor, etc.)

Additional Notes

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[ajf]

/ok to test dd771ef

[ajf]

@shevchenko-evgeny: to pass the DCO (Developer Certificate of Origin), add the Signed-Off-By: git header in the commit with git commit -s

[shevchenko-evgeny]

@ajf The commit has been signed per your request.

The build-release-container-x86_64 task is currently failing on carbide-ssh-console --test main. I suspect the build container does not have ipmi_sim and ipmitool installed. Addressing that is outside the scope of this fix.

[ajf]

/ok to test ba84966

[ajf]

@shevchenko-evgeny this LGTM, but I need to check internally if we're actually enforcing commit signatures for non-NVIDIA org people.

[ajf]

@shevchenko-evgeny yes, looks like we need your commit signed before merging (https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#ssh-commit-signature-verification)

[shevchenko-evgeny]

@ajf signed