Add dev branch docker images to registry

[Curious-r]

Description

This PR will provide images with "dev" tag in dockerhub and ghcr. After this change, the "latest" tag in registry will point to the newest release, and "dev" tag will point to the image with the last commit in dev branch. #

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)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Curious-r]

PTAL @kfiven

[Curious-r]

I have read the CLA Document and I hereby sign the CLA

[kfiven]

Hi, thanks for working on this. Can we please not run this on every commit as this would be very resource intensive. I think once a week or something similar would be best for this action.

[Curious-r]

Sorry for the late reply. I have make an update, add a job to ensure that the interval between image publishes is greater than a week.
And there is a question: is DOCKER_PASSWORD a Docker Hub token? Although it doesn't matter even if it's ineffective, I'm just using it to avoid the rate limit of API requests.
Thanks!

[kfiven]

Hi, no worries! Can we setup it like a separate action and do the schedule part as explained in Action docs as it seems much easier.

[Curious-r]

'docker/metadata-action' and 'docker/build-push-action' use git ref of the event that triggers the workflow to automate a lot of things, changing to schedule, we need to configure it in a more complex way.
Or we can just delete -H "Authorization: Bearer ${{ secrets.DOCKER_PASSWORD }}" in curl command, our use case doesn't cause rate limiting.