ci: build and test

[a-frantz]

Describe the problem or feature in addition to a link to the issues.

Fixes the CI for the hundredth time this week (and hopefully the last time).

Before submitting this PR, please make sure:

• You have added a few sentences describing the PR here.
• You have added yourself or the appropriate individual as the assignee.
• You have added at least one relevant code reviewer to the PR.
• The code passes all CI tests without any errors or warnings.
• You have added tests (when appropriate).
• You have added an entry in any relevant CHANGELOGs (when appropriate).
• If you have made any changes to the scripts/ or docker/ directories, please ensure any image versions have been incremented accordingly!
• You have updated the README or other documentation to account for these changes (when appropriate).

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[adthrasher]

I don't think it's important, but I wonder if the tag list could be passed between the workflows. It's cheap to recompute, so it's more a curiosity.

[adthrasher]

Good catch on both of these. Definitely the preferred behavior.