Sharedasset detection using checksum can fail when switching between proton and native on second install [no fix needed?]

For some chapters (eg. ch8), installer chooses sharedassets depending on the checksum of the original sharedassets0.assets.

Because our installer overwrites the sharedassets0.assets file, we also check the checksum of the sharedassets0.assets.backup file to see the "original" sharedassets file. This .backup file is created by our installer when you install the mod.

However, if you:

- First install using say Proton, it will create a sharedassets0.assets.backup file from the Proton install.
- Switch back to Native. This will overwrite the sharedassets0.assets with the Native version
- Perform an install of the mod the first time, the install will work OK (it will overwrite the sharedassets0.assets with the mod version)
- Because a .backup file already exists, this install won't overwrite the sharedassets0.assets.backup file
- Now, when you perform the second install or update, the sharedassets0.assets will be the mod version, which the installer does not recognise. Also, the sharedassets0.assets.backup file is from the Proton install, which the mod also does not recognize. This will cause an install error.

查看安裝程式的共享資源偵測邏輯，很可能在處理校驗和或資源管理的檔案中。該問題描述了一個情境：來自 Proton 安裝的備份檔案 (sharedassets0.assets.backup) 在後續的 Native 安裝上導致不匹配。首先找到為 sharedassets0.assets 及其備份計算校驗和的位置。理解安裝流程以查看備份是如何建立以及何時被覆蓋的。測試涉及模擬在 Proton 和 Native 模式之間切換的安裝。

由索引模型根據 Issue 內容生成。