Fix CI Nits

[ian-noaa]

This PR does a bit of upkeep on our CI:

• Builds the home app for git tags
• Adds a job to clean up home app PR images
• Adds the home app to the workflow that cleans up untagged container images
• Adds the home app to the deploy job
• Updates Dependabot to use development as the base branch instead of main for home app updates
• Retires the add-issue-to-project.yml job - this is now built-in to the project board
• Fixes a harmless but annoying failure where the PR container image cleanup workflow tried to cleanup non-existent MATS container images after a home app update
• Adds CodeQL checks for our Go code
• Standardizes home app/mats app CI workflow names

[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.

[mollybsmith-noaa]

Looks good to me, but can you do the same for the METexpress repo so they stay equivalent? Thanks for handling this!

[ian-noaa]

Thanks for the review!

These changes were focused on accommodating the new home app. That app doesn't exist in the METexpress repo so there isn't much to do there - CI will continue to function normally.

[mollybsmith-noaa]

If there weren’t any non-home-app changes in addition then we should be good. It’s just nice if they all match in terms of settings, timeouts, etc.

…

On Wed, Jan 17, 2024 at 12:19 PM Ian McGinnis ***@***.***> wrote: Thanks for the review! These changes were focused on accommodating the new home app. That app doesn't exist in the METexpress repo so there isn't much to do there - CI will continue to function normally. — Reply to this email directly, view it on GitHub <#1144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHBWGZOVRCE6X2G52QYDS4LYPAP4XAVCNFSM6AAAAABB5NS34WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJWGQ4DAMBRGY> . You are receiving this because your review was requested.Message ID: ***@***.***>

[ian-noaa]

I double checked and it appears that GitHub projects can now interact with issues from across organization boundaries. I'll go ahead and remove the add-issue-to-project CI job in METexpress.