fix(cache): isolate cache keys per provider name and options

[sushichan044]

fixes #184

This PR updates the cache storage generation to automatically include the provider name and options in the cache key.
Users don’t need to do anything special when defining a provider.

Additional Context

Purpose 1 of #239 (comment).

[sushichan044]

For example, if we also hash values like the font provider’s name, it becomes difficult to identify files when checking what Storage has saved. So I think we shouldn’t hash string fields.

[sushichan044]

@danielroe
I think this implementation safely isolates the cache between providers, noted in #239.
I’m still keeping an eye on the changes being discussed in #287 and #288.
Could you review the design?

[sushichan044]

Since the commit history became too cluttered and conflicted with other PRs, I used a force push.

[danielroe]

apologies for going back and forth on this.

we should definitely cache by key (font provider) + version of unifont.

my one reservation is that caching uniquely by options too, may be over-unique. for example, google fonts will have the same list of fonts, regardless of what options are passed to it. so I'd like to refactor later on to allow providers a little more control over what is dependent on the options and what isn't...

however, I think this is looking really good, and I don't want to hold it up, so I think we can merge and iterate (if you're happy to address the merge conflict 🙏

thank you for your work on this

[sushichan044]

Thanks!
I’ll watch the other PRs and keep iterating on improvements after this one is merged.

[sushichan044]

Conflict resolved in https://github.com/unjs/unifont/compare/9f764a10cd601db0add398a6f730db8cbb7cd5f0..1113b6febd3f96d2b4b5d3c69ad180e8f22f642d

This diff is safe because it doesn’t affect any cache-related test cases and CI passes without differences.