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.

Comienza con el método getCacheId de la clase Config en el prototipo nanoColor e inspecciona cómo serializa actualmente la configuración a Yaml. Determina un reemplazo estable que no requiera Yaml y defina cómo debe afectar un reordenamiento trivial al ID; se considera terminado cuando el código cliente pueda calcular una Config cacheID sin la dependencia eliminada.

Escrito por el modelo de indexación a partir del texto del issue.