drone(docker-driver): Fetch tags before pushing image during release

[kavirajk]

What this PR does / why we need it:
We realized, loki-docker-driver image was not being pushed after 2.8.2. And looking into it's drone pipeline and comparing it with other steps, docker-driver step is not fetching the tags, thus the final hash calculated to push is some HEAD branch.

e.g: even if we have tag 2.9.1, it pushes only with latest HEAD commit hash.

This PR fixes it.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:
I would prefer this instead of #10663. Because that would make fetching tags more repetitive in all the drone tasks (can also be expensive in terms of running time if we put all together)

Checklist

• Reviewed the CONTRIBUTING.md guide (required)

[kavirajk]

tried one more approach before this.

Tried to add it as separate step say fetch-git-tags on this pipeline. In that case, git tags only fetched in that particular step and cannot be used during make docker-driver-push step. Rationale being other pipelines that do use separate step to fetch git tags, stores it in ./tools/image-tag > arch.tags and re-use it other step.

Ended up doing this way without changing much of the pipelines.

[dannykopping]

LGTM but you'll need to update the drone signature

[grafanabot]

The backport to release-2.8.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-10664-to-release-2.8.x origin/release-2.8.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 8721e41c6c36910d60cdc2c1253bded0058fd493
# When the conflicts are resolved, stage and commit the changes
git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-10664-to-release-2.8.x
# Create the PR body template
PR_BODY=$(gh pr view 10664 --json body --template 'Backport 8721e41c6c36910d60cdc2c1253bded0058fd493 from #10664{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[release-2.8.x] drone(docker-driver): Fetch tags before pushing image during release" --body-file - --label "size/XS" --label "type/bug" --label "backport" --base release-2.8.x --milestone release-2.8.x --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-10664-to-release-2.8.x

# Create a pull request where the `base` branch is `release-2.8.x` and the `compare`/`head` branch is `backport-10664-to-release-2.8.x`.

# Remove the local backport branch
git switch main
git branch -D backport-10664-to-release-2.8.x