[CI/CD] Improve assertion doc generation

[sean-breen]

Proposed changes

Adds the assertion document generation as an option when running the release branch workflow.

For the assertion doc, we need to generate a few extra files to pass along, mainly:

• sha checksum
• build start time
• build end time

These get stored in files alongside the binary which is created in make package, and these files along with the binary itself are stored to GitHub artifacts.

When 'Store assertion document' option is selected:

• The Assertion document workflow then downloads the artifacts from the calling pipeline, runs the dependency analysis and generates the document.

When running the Assertion doc workflow manually:

• Supply the Run ID of the pipeline which created the build artifacts, if they are still in GitHub the workflow will download these, and proceed with the workflow as normal.

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING document
• I have run make install-tools and have attached any dependency changes to this pull request
• If applicable, I have added tests that prove my fix is effective or that my feature works
• If applicable, I have checked that any relevant tests pass after adding my changes
• If applicable, I have updated any relevant documentation (README.md)
• If applicable, I have tested my cross-platform changes on Ubuntu 22, Redhat 8, SUSE 15 and FreeBSD 13

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.27%. Comparing base (db165d2) to head (4e2ee6b).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1400   +/-   ##
=======================================
  Coverage   86.27%   86.27%           
=======================================
  Files         102      102           
  Lines       12622    12622           
=======================================
  Hits        10890    10890           
  Misses       1253     1253           
  Partials      479      479           

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 540ed2f...4e2ee6b. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.