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 の本文から書いたものです。