[Bug] 同步或导入低版本的备份后，导致可选模型列表被修改

[benvyeng]

Bug Description

目前使用docker安装2.12.3版本。当使用之前导出的本地json或upstash同步后，旧版本的设置覆盖新版本的model可选列表。导致可选用的新模型消失，最明显的就是新添加的gpt-4o和gpt-4o20240513从任何地方都找不到了，包括设置-model选择、对话窗口model选择、编辑面具model选择。这些地方都找不到新的模型了。
查看浏览器本地存储发现，app-config键中存储了model的列表，猜测是被同步和备份数据覆盖了。
模型列表被覆盖应该是违反了现实逻辑，应该不做同步处理，或者在后端写死

Steps to Reproduce

1.docker安装好2.12.3版本的应用
2.浏览器清空缓存
3.检查设置窗口-model选择，可以看到gpt-4o待选
4.点击设置好upstash并同步或者导入本地数据（之前的备份）
5.再次检查设置窗口-model选择，gpt-4o和gpt-4o20240513的选项消失了

Expected Behavior

恢复备份和同步只涉及对话数据和面具，不应对模型列表进行操作。这样实际是造成了功能的回退。

Screenshots

Deployment Method

• Docker
• Vercel
• Server

Desktop OS

windows 10

Desktop Browser

Chrome

Desktop Browser Version

124.0.6367.158

Smartphone Device

No response

Smartphone OS

No response

Smartphone Browser

No response

Smartphone Browser Version

No response

Additional Logs

No response

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: [Bug] After synchronizing or importing a backup of a lower version, the optional model list is modified.

[Dean-YZG]

非常感谢反馈，这个问题产生的原因是，目前『同步功能』实现的逻辑是：同步功能被封装成一个完全独立的模块， 不理解各个数据参数间的业务逻辑关联性，仅简单地对远端和本地的数据进行同名变量合并，因此，造成一些不应做简单合并的状态参数被简单合并了。目前可以先通过自定义模型的方式来解决这个问题，我们会尽快设计合理的同步数据合并方案，彻底解决该问题

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Thank you very much for the feedback. The reason for this problem is that the current implementation logic of the "synchronization function" is: the synchronization function is encapsulated into a completely independent module. It does not understand the business logic correlation between each data parameter, and only simply Merge variables with the same name with local data. Therefore, some status parameters that should not be simply merged are simply merged. Currently, this problem can be solved by customizing the model. We will design a reasonable synchronization data merging solution as soon as possible to completely solve this problem.