ci: validate build jobs

[reubenmiller]

Proposed changes

Add ci checks to validate if any of the build matrix jobs was marked as failed, cancelled, or skipped.

It has been observed that if a Github Runner fails on one of the build matrix jobs, it can lead to the job being skipped, which in turns is treated by the workflow as a "don't care". This leads to the publishing jobs only partially publishing all of the expected packages (from those build jobs which passed), see an example .

References:

• https://github.com/orgs/community/discussions/26822

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

#2908

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s)
• I ran cargo fmt as mentioned in CODING_GUIDELINES
• I used cargo clippy as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.1%. Comparing base (613e8dd) to head (0b974d5).
Report is 1 commits behind head on main.

Additional details and impacted files

see 2 files with indirect coverage changes

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
444	0	3	444	100	1h2m11.311539s