fix(fonts): handle urls without extensions

[florian-lefebvre]

Changes

• Closes Unable to use the experimental font API with Typekit #13743
• Until this PR, we assumed the font files urls returned by providers would end with a file extension eg. .woff2
• However this is not always the case (eg. adobe)
• To fix this, I moved the type extraction so that remote providers and local providers handle it differently
  • local provider: keep the previous behavior ie. extract the type from the url
  • remote provider: try use source.format (given by unifont) then fallback to extracting the type from the url

Testing

Tests updated and added. Affected user confirmed it works using the preview release

Docs

Changeset

[changeset-bot]

🦋 Changeset detected

Latest commit: f868f26

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 #13752 will not alter performance

_{Comparing fix/fonts-urls-without-extension (f868f26) with main (d874fe0)}

Summary

✅ 6 untouched benchmarks

[pkg-pr-new]

astro

npm i https://pkg.pr.new/astro@13752

@astrojs/cloudflare

npm i https://pkg.pr.new/@astrojs/cloudflare@13752

@astrojs/netlify

npm i https://pkg.pr.new/@astrojs/netlify@13752

@astrojs/node

npm i https://pkg.pr.new/@astrojs/node@13752

@astrojs/vercel

npm i https://pkg.pr.new/@astrojs/vercel@13752

commit: f9d3ec4