chore(deps): update clickhouse/clickhouse-server docker tag to v25.1.2

[renovate]

This PR contains the following updates:

Package	Update	Change
clickhouse/clickhouse-server	patch	25.1.1-alpine -> 25.1.2-alpine

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

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: Never, 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 was generated by Mend Renovate. View the repository job log.

[f2c-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[f2c-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[wanghe-fit2cloud]

The provided diff indicates an update from the ClickHouse server version 25.1.1-alpine to 25.1.2-alpine. Here's a concise analysis:

Irregularities/Potential Issues:

• The diff is simply listing an updated image tag without specifying which file or section it pertains to in your configuration.

Optimization Suggestions:

• Ensure that if you plan on using this service with other similar configurations (e.g., Docker Compose), make sure all changes are consistent across files. In this case, updating the image tag should be applied consistently throughout any relevant YAML files.

If you need further assistance tailored to your specific use case or have additional context, feel free to ask!