Backport of build(docker): always publish full and minor version tags for dev images into release/1.1.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #306 to be assessed for backporting due to the inclusion of the label backport/1.1.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@DanStough
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul-dataplane/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Always publishing full and minor-only tag versions. This accomplishes two goals:

1. For long running release branches, .x, always publish a minor-only tag so that tests use the latest version (e.g. 1.4-dev)
2. For point release branches, .0, always publish the full version so we can fix this for testing purposes (e.g. 1.3.0)

---

Overview of commits

• d51f752

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}