自 0d79712 出現問題：新增的補丁文件不加載、生成棱鏡出錯

[mrhso]

症状：

• 用户文件夹中的方案失效。
• 生成的棱镜有问题，拼写运算部分失效。

[lotem]

463dc09 對症嘛？

[lotem]

先粗略羅列出直接創建 Config 對象而非通過 ConfigComponent 加載的代碼以待排查。

• tools/rime_dict_manager.cc - safe
• tools/rime_deployer.cc - safe
• test/config_test.cc - safe
• test/encoder_test.cc - safe
• src/rime/lever/customizer.cc - DEPRECATED
• src/rime/lever/switcher_settings.cc - VULNERABLE
  SwitcherSettings::GetAvailableSchemasFromDirectory()
• src/rime/lever/custom_settings.h
• src/rime/lever/deployment_tasks.cc - safe; with concerns
• src/rime/lever/custom_settings.cc - VULNERABLE
• src/rime_api.cc - safe

[Prcuvu]

463dc09 是为了解决 WeaselDeployer 不能正确获取已选方案列表的问题，不解决 Config 组件的其他问题。

[lotem]

發現一個疑似問題：
__build_info 記錄了上次編譯引用的源文件的 config_id，但是如果添加了自動（通過插件）引用的自定義文件 *.custom.yaml，由於不需要改動入口文件（對比顯式引用需添加 __include: 或 __patch: 語句從而可檢測到入口文件更新），新文件不會納入檢查。

[lotem]

The current implementation of CustomSettings and SwitcherSettings is flawed. If we introduce external references in the bundled YAML files, then CustomSettings::config_ loads incomplete shared data.
To fix this, we should either use a (read-only) ConfigBuilder in CustomSettings and SwitcherSettings, or change the Windows installer to call Configurator after an initial deployment and make the user copy available.

[lotem]

Maybe we should pre-build shared data for Weasel, as @nameoverflow suggested.
It is easier and more economic than employing a read-only ConfigBuilder in CustomSettings.
Another reason I didn't mention in 463dc09 was:
With the old logic, the IME run-time only reads data form user directory, whereas the pre-built data are in shared data directory. In Unix-like systems those pre-built data files are quickly symlinked to user data directory, but on Windows the filesystem doesn't always support links. I preferred deploying in user data directory during install to copying files around. Now it's no longer a problem thanks to fallback directory support.

[lotem]

Thanks for testing. There is now a fix.

Reminder:

• Please only send new builds to testers (who can save themselves) until a new release is marked.
• Before trying the new build, you need to manually delete the directory $RIME_USER_DIR/build in case broken config files (generated by the previous build) cannot be correctly patched.