Fix: Correction to the full name of Volc TOS

[jneless]

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Fix typo in TOS full name

According to VolcEngine and BytePlus Doc, the TOS full name is "Torch Object Storage", instead of Tinder.
Modify the full name of TOS, in middleware/storage/volcengine_tos_storage.py

Reference:

• https://www.volcengine.com/docs/6349?lang=zh
• https://docs.byteplus.com/en/docs/tos/docs-what-is-tos

Screenshots

Before	After
...	...

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran make lint and make type-check (backend) and cd web && npx lint-staged (frontend) to appease the lint gods

[gemini-code-assist]

Summary of Changes

Hello @jneless, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request rectifies an inaccurate full name for VolcEngine's Object Storage (TOS) within the system's configuration. By updating the name from "Tinder Object Storage" to the correct "Torch Object Storage," the change enhances the accuracy and consistency of the codebase, aligning it with official vendor documentation.

Highlights

• Typo Correction: Corrected the full name of Volc TOS from "Tinder Object Storage" to "Torch Object Storage".
• Accuracy Improvement: Ensures the system's configuration accurately reflects the official naming from VolcEngine and BytePlus documentation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[jneless]

typo fix, no additional test-case and no existing test-case change

[gemini-code-assist]

Code Review

This pull request corrects a typo in the full name of Volcengine TOS, changing 'Tinder' to 'Torch' in the configuration file's docstring. The change is accurate according to the provided documentation links. I've reviewed the change and it correctly addresses the typo. I also checked other related files for similar typos and found none, so the fix appears complete. The change is good to merge.