chore(deps): update bytebase/bytebase docker tag to v3.5.3

[renovate]

This PR contains the following updates:

Package	Update	Change
bytebase/bytebase	patch	3.5.2 -> 3.5.3

---

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.

Details

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.

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

[wanghe-fit2cloud]

The code difference seems to be minor changes in the version number from 3.5.2 to 3.5.3. These versions typically only include bug fixes or improvements in the application without major architectural updates. There are no irregularities, potential issues, or optimizations needed at this time; only a change in one of the service parameters (image tag).

Here's an example of how the configuration might look if there were other changes:

@@ -1,6 +1,8 @@
 services:
   bytebase:
     image: bytebase/bytebase:3.5.3
+    ports:
+      - "8000:80"
     container_name: ${CONTAINER_NAME}
     restart: always
+    environment:
+      DB_HOST: my_database_host
     networks:

Again, no special considerations required given that the update is just a patch release.