No automatic docker container on new release

**What problem are you trying to solve? Please describe.**
There is a docker publishing workflow but it doesn't automatically run and publish on new releases. As a result, the latest image in the registry is not up to date with the latest release.

**The ideal solution: What should the feature do?**
Improve the docker workflow so it automatically runs on tag pushes and publishes an appropriately-named container.

**What category of feature is this?**

- [ ] UI/UX
- [ ] API
- [x] Other

**If you have code or pseudo-code please provide:**
N/A

- [x] Willing to submit a pull request to implement this feature?

**Additional context**
I have submitted a PR to implement this feature: https://github.com/apache/caldera/pull/3416.

Start with the existing Docker publishing workflow and inspect its current triggers and image naming. Update it so tag pushes run the workflow and publish the appropriately named container, then verify the workflow configuration and release-trigger behavior.

Written by the indexing model from the issue text.