ci: add explicit dependency on build job

[reubenmiller]

Proposed changes

Note: still needs to be tested by running through the merge queue

Prevent progression of the workflow if a build job is cancelled or skipped.

Without a direct link to the publish and build jobs, the publish was previously triggered if the test job was marked as skipped (due to its upstream job being not marked as "success").

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 (05a644e) to head (613e8dd).
Report is 5 commits behind head on main.

Additional details and impacted files

see 5 files with indirect coverage changes

[github-actions]

Robot Results

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

[didier-wenzek]

Approved