Feature Request: Support Github TAG as Registry TAG

What problem will this feature address?

Currently, if I have a flow that generates a new tag on github and that I have dokploy set to deploy ON TAG, if the rollback registry is configured (In this case let's imagine it's ghcr) Dockploy won't use the same tag as my Github Tag which makes it harder to track rollback and deployements.

Describe the solution you'd like

It would be nice to have a possible configuration in the rollback or when you set the deploy to run 'ON TAG' to let dokploy use that same tag when pushing the image to the registry.

Describe alternatives you've considered

I consider using Github action to also push to the registry and disabling automatic push to registry on dokploy and then switch the provider to Docker but that would be tideious to do and i'd love to have a simpler solution

Additional context

No response

Will you send a PR to implement it?

No

Start by tracing the ON TAG deployment path and rollback registry configuration in the TypeScript codebase, then inspect how GitHub tags and registry image tags are currently handled. Done means a documented configuration lets deployments use the same tag for the GitHub release and pushed registry image, including rollback behavior.