feat(apps/gcp/prow/release): bump tide image tag to v20260520-5d43b45c8

[wuhuizuo]

[Copilot is generating a summary...]

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign dillon-zheng for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

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

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Summary:
This PR updates the tide image tag in the Prow release manifest from v20260224-5ba85b827 to v20260520-5d43b45c8, effectively bumping the tide component to a newer version. The change is minimal and straightforward, focusing solely on upgrading the container image version. The patch is clean and follows expected practices for version bumping in Kubernetes manifests.

---

Best Practices

• File: apps/gcp/prow/release/release.yaml (line 86)
  Issue: The PR lacks any accompanying changelog or explanation for the image tag update.
  Why: While the version bump itself is simple, it is best practice to document what changes or fixes the new tide version includes to provide context for reviewers and future maintainers.
  Suggestion: Add a brief note in the PR description or a changelog file summarizing the changes or benefits of the new tide version (e.g., bug fixes, performance improvements, security patches).

• File: apps/gcp/prow/release/release.yaml (lines 87-89)
  Issue: The additionalArgs flags --sync-hourly-tokens and --status-hourly-tokens are left unchanged but might benefit from a comment or verification against the new tide version capabilities.
  Why: When bumping versions, flags or defaults might change. Confirming they are still valid or optimal with the new version avoids configuration drift or deprecated usage.
  Suggestion: Confirm in documentation or release notes of the tide version that these flags remain recommended. Optionally add comments referencing the version they apply to.

---

No critical issues or code improvements are applicable given the very limited and focused nature of this PR. Overall, this is a clean and minimal version bump with no functional or structural problems.