feat(fonts): update unifont

[florian-lefebvre]

Changes

• Updates unifont to 0.4.0 (latest)
• Adds support for passing fetch init (see feat: add meta.init type to FontFaceData unjs/unifont#155)
• Refactors types a bit to avoid duplication
• For init, I chose to use null instead of an optional property to make sure we pass it through everything

Testing

• Updated tests so they still pass and TS is happy
• Updated the orchestrate test to make sure init is well forwarded to the end

Docs

Changeset

[changeset-bot]

🦋 Changeset detected

Latest commit: 690edae

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codspeed-hq]

CodSpeed Performance Report

Merging #13705 will not alter performance

_{Comparing feat/fonts-update-unifont (690edae) with main (60d5be4)}

Summary

✅ 6 untouched benchmarks

[ematipico]

Can we have a JSDoc and a return type for the orchestrate function? It's very big, we don't know what it does (orchestrate is a very generic term), and now we changed its return type, where we also changed internal variables, in which some comments were lost

[florian-lefebvre]

The orchestrate function already has jsdocs explaining what happens inside. So to address your review, here is what i've done:

1. I've specified an explicit return type
2. I copied the comments from the types to the variables inside orchestrate

Because yes comments were not lost but moved to types.ts. Hope that helps but let me know if that's not enough, I'm happy to clarify anything!

[ematipico]

Thank you! Apologies I missed the JSDoc attached to the function