Update images digests

[kylos101]

Update images digests using the latest version available for image/s

How to test

Start a workspace in the preview environment and verify that it functions properly.

Preview status

gitpod:summary

Preview Environment / Integration Tests

/werft with-preview

/werft with-gce-vm If enabled this will create the environment on GCE infra

/werft preemptible Saves cost. Untick this only if you're really sure you need a non-preemtible machine.

with-integration-tests=ssh Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.

[ona-integrations]

Reviewed the changes. Implementation looks solid: the PR mechanically rotates two pinned image digests (the chainguard/helm installer base image and the oliver006/redis_exporter ExporterImageDigest) and correctly preserves the repository's digest-pinning pattern. No significant code-quality concerns.

Docs review: ran as a docs-drift check only (code-only PR); no documentation updates are required, as digest values are internal build/deployment pins and no user-visible behavior, API, config, or operational surface changed.

Low-risk determination: Escalate to human review
This change does not meet all low-risk criteria or has review findings requiring human attention before merge.

• Size: pass — additions + deletions = 4 lines, far below the 1,000-line threshold.
• Protobuf: pass — no .proto files added or modified.
• Database migrations: pass — no migration files added or modified.
• Infrastructure/CI: pass — the Dockerfile change is a base-image digest rotation (dependency pin update), not an infrastructure, platform, or CI configuration change.
• Auth and authorisation: pass — no auth or access-control logic affected (no RBAC, roles, permissions, scopes, policies, guards, ACLs, or session handling touched).
• Audit logging and monitoring: fail — ExporterImageDigest for oliver006/redis_exporter, a Prometheus metrics/monitoring exporter, is rotated to a new digest. This swaps the running monitoring component to a different upstream build, and the diff does not confirm the version mapping or that emitted metrics remain compatible, so criterion 6 (which explicitly covers monitoring and metrics) cannot be confidently cleared.