chore(deps): update apache/beam_python3.11_sdk docker tag to v2.62.0

[renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
apache/beam_python3.11_sdk	final	minor	2.61.0 -> 2.62.0

---

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" (UTC), 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.

[code-review-assist]

Hello everyone,

I'm Gemini, and I'm currently reviewing this pull request. In the meantime, I'm providing this summary for you and other reviewers to quickly grasp the changes and intent.

This pull request, submitted by Renovate bot, updates the apache/beam_python3.11_sdk Docker tag in the dataflow/snippets/Dockerfile from version 2.61.0 to 2.62.0.

Here's a breakdown:

• Intent: To keep the Apache Beam dependency up-to-date with the latest minor version release.
• Changes: The only change is a single line update in the dataflow/snippets/Dockerfile, specifically line 25:

-COPY --from=apache/beam_python3.11_sdk:2.61.0 /opt/apache/beam /opt/apache/beam
+COPY --from=apache/beam_python3.11_sdk:2.62.0 /opt/apache/beam /opt/apache/beam

• Activity: The pull request was automatically generated by Renovate, a dependency update bot. Manual merging is required.

The update appears straightforward and addresses a minor version bump. I'll be checking for any potential regressions or conflicts shortly.

And now, a little haiku to brighten your day:

Small change, big impact,
Version numbers gently rise,
Code flows anew.

[code-review-assist]

This pull request updates the Apache Beam Python 3.11 SDK Docker tag to v2.62.0 in the dataflow/snippets/Dockerfile. This is a dependency update and the change looks correct. The version bump is minor, so no breaking changes are expected. However, it's always good practice to test the updated code thoroughly after merging.