config ci: Features/Fixes to Help UX

[CodeGat]

Now that devs (@dougiesquire 👀) are using the workflow, there are some features being requested (and I'll add a couple more nice-to-haves from my own perspective, too). This issue can be a general dumping ground for features until we create a Zenhub Epic.

• Have links to both the compared checksum directory (will be a hyperlink to the GitHub repo in testing/checksum at the compared Config Tag) and the current PR checksum directory (at that point will be an artifact, so will be a download link and a cd testing/checksum directive) in the Bitwise Reproducibility comment. See Checksum Links in Comments #34
• Rather than needing to rebase the dev-* onto release-* every time we have a new release-* config, search for the previous release-* config tag on the ${{ github.base_ref }} rather than the ${{ github.head_ref }}. Since we have a well-defined naming scheme, it should be easy to checkout. See Compare Checksum from release-* rather then the PR Branch #35
• Investigate the suitability of dev-* branches at all - we seem to immediately merge into release-* anyway. If we need to have somewhere to develop and work on configurations, why not just use the PR branch? Look into previous discussions for the rationale. See Add Repro Checks to dev-* branches #38 and a future issue.
• Consider removing the Create Initial Checksum workflow for the initial development of checksums. The workflow actually gets quite far along without a checksum to compare to, so it might be worth just allowing people to merge to the release-* branch without a checksum to compare against. See Remove generate-checksums.yml Workflow #36

Please feel free to comment on this issue for further improvements that can be made to the workflow.

[CodeGat]

Closing this as tasks have either been turned into their own issues, or completed.