fix(release-v3.5): Update docker-compose.yml

[cubxxw]

🔍 What type of PR is this?

/kind documentation
/kind feature

👀 What this PR does / why we need it:

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

This Pull Request (PR) is essential for several reasons:

1. Improving Deployment Quality: By merging the latest and most efficient deployment scripts from the main branch, we aim to enhance the deployment processes in the release-v3.5 branch. This ensures that we are utilizing the best practices and most recent improvements in our deployment strategy.

2. Maintaining Consistency: Keeping the deployment scripts consistent across different branches helps in standardizing our deployment processes. This is crucial for seamless integration and continuous development practices.

3. Ensuring Stability and Efficiency: The main branch often contains the most updated and tested scripts. Merging these into the release-v3.5 branch helps maintain the stability and efficiency of our deployments in this branch, which is likely being used for more stable, long-term releases.

4. Pre-emptive Problem Solving: By integrating these changes now, we can identify and address any potential issues in the release-v3.5 branch early, preventing more significant challenges down the line.

Overall, this PR is a proactive step towards maintaining high-quality, efficient, and consistent deployment practices across our branches.

🅰 Which issue(s) this PR fixes:

Fixes #1773

📝 Special notes for your reviewer:

🎯 Describe How to Verify It

To verify the effectiveness of this PR, follow these steps:

1. Refer to the OpenIM Deployment Guide: Utilize the detailed instructions provided in the OpenIM Deployment Guide. This guide should offer a step-by-step process for deploying the scripts on a server environment.

2. Execute the Deployment on a Server: Carefully execute the deployment process on a server as per the instructions in the guide. Make sure to replicate the environment and conditions of the release-v3.5 branch as closely as possible for accurate verification.

3. Verification Criteria: The verification is considered successful if the deployment is executed without any errors and if the server operates as expected after the deployment. Pay close attention to any deviations from expected behavior or performance issues that might arise.

4. Document the Process and Results: Keep a detailed record of the deployment process and any observations. This documentation will be crucial for understanding the impact of the changes and for any future troubleshooting.

By following these steps, we can ensure that the deployment scripts merged into the release-v3.5 branch are robust and function as intended.

📑 Additional documentation e.g., RFC, notion, Google docs, usage docs, etc.:

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: All new business logic should have corresponding unit tests.
• Apply: Refactor large functions to be more modular.
• Apply: Add docstrings to all functions and file headers.

This is an automated message generated by Sweep AI.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (820bf83) 5.10% compared to head (8e5e792) 5.10%.
Report is 16 commits behind head on release-v3.5.

Additional details and impacted files

@@             Coverage Diff              @@
##           release-v3.5   #1774   +/-   ##
============================================
  Coverage          5.10%   5.10%           
============================================
  Files                42      42           
  Lines              3797    3797           
============================================
  Hits                194     194           
  Misses             3592    3592           
  Partials             11      11           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sweep-ai]

Fixing PR: track the progress here.

I'm currently fixing this PR to address the following:

[Sweep GHA Fix] The GitHub Actions run failed with the following error logs:

[!CAUTION]

An error has occurred: Sweep could not find any files to modify (tracking ID: 4359b99246)

[longyuqing112]

[kubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

[longyuqing112]

Title: fix(release-v3.5): Update docker-compose.yml
Translation: "Fix(release-v3.5): Update docker-compose.yml"