Improve config cacheID algorithm to not require Yaml

In the nanoColor prototype, the getCacheId method on the Config class is not working properly. This is because it is generating the ID by serializing the config to Yaml and then calculating a hash of that. Since nanoColor removes the Yaml library, this no longer works. This task is to come up with an alternate mechanism for generating a Config cacheID.

The Yaml-based mechanism is arguably not ideal anyway since reordering color spaces and other trivial changes would change the ID. If people have thoughts on how they would like the Config cacheID to be calculated, please add a comment below.

Note that the Config cacheID is not used internally to the library itself, so this is something that strictly affects client code.

从 nanoColor 原型中的 Config 类的 getCacheId 方法开始，检查它当前如何将配置序列化为 Yaml。确定一种不需要 Yaml 的稳定替代方案，并定义简单的重新排序应如何影响 ID；当客户端代码可以在不使用已移除依赖项的情况下计算 Config cacheID 时，即表示完成。

由索引模型根据 Issue 内容生成。