Chore: Simplified registry cleanup

[stumpylog]

Proposed change

It always annoyed me the cleanup for our installer images was checking the feature- existence, when that's not relevant. So I've rewritten the cleaning to be class based, with only the main image and its cache caring about feature-* branches. The logic is otherwise the same logic as before.

I also updated the workflow to run more in parallel, and included the confirmation step of all images pulling after cleaning for everything which gets cleaned.

I know it's still probably complicated, so if I can diagram or explain something more in the files to help with understanding, let me know.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (please explain) - Maintenance

Checklist:

• I have read & agree with the contributing guidelines.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• If applicable, I have checked that all tests pass, see documentation.
• I have run all pre-commit hooks, see documentation.
• I have made corresponding changes to the documentation as needed.
• I have checked my modifications for any breaking changes.

[shamoon]

I dont know if others feel differently (Bueller?) but I'm happy to take your word for it on this one, if it works it works...

[stumpylog]

I know, I've learned a bunch about the registry and the GitHub API. If I knew Javascript, I'd package the logic up into an action.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.