chore(deps): update golang docker tag to v1.21.3 (main)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
golang	final	patch	1.21.2-bullseye -> 1.21.3-bullseye

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

Building new version of mimir-build-image. After image is built and pushed to Docker Hub, a new commit will automatically be added to this PR with new image version `grafana/mimir-build-image:pr6325-d6fe286995`. This can take up to 1 hour.

[github-actions]

Not building new version of mimir-build-image. This PR modifies `mimir-build-image/Dockerfile`, but the image `grafana/mimir-build-image:pr6325-d6fe286995` already exists.

[pstibrany]

Makefile update with grafana/mimir-build-image:pr6325-d6fe286995 is missing.

[aknuds1]

That's a weird glitch @pstibrany, maybe it's because the automation got interrupted.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[github-actions]

Not building new version of mimir-build-image. This PR modifies `mimir-build-image/Dockerfile`, but the image `grafana/mimir-build-image:pr6325-d6fe286995` already exists.

[pstibrany]

Thank you.

[colega]

This should be backported to 2.10 to release 2.10.1

[grafanabot]

The backport to release-2.10 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-6325-to-release-2.10 origin/release-2.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x ed62c6eb7ee8efceda0081713e668265505ebe6e
# Push it to GitHub
git push --set-upstream origin backport-6325-to-release-2.10
git switch main
# Remove the local backport branch
git branch -D backport-6325-to-release-2.10

Then, create a pull request where the base branch is release-2.10 and the compare/head branch is backport-6325-to-release-2.10.

[colega]

I'll do the backport manually.

[aknuds1]

Backport is already done @colega.

[grafanabot]

The backport to release-2.9 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-6325-to-release-2.9 origin/release-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x ed62c6eb7ee8efceda0081713e668265505ebe6e
# Push it to GitHub
git push --set-upstream origin backport-6325-to-release-2.9
git switch main
# Remove the local backport branch
git branch -D backport-6325-to-release-2.9

Then, create a pull request where the base branch is release-2.9 and the compare/head branch is backport-6325-to-release-2.9.