Fix NextFontIssue IssueStage: CodeGen → Resolve

[sokra]

What?

Changes NextFontIssue's IssueStage from CodeGen to Resolve.

Why?

NextFontIssue is emitted during font resolution — when validating font configuration options (util.rs) and when fetching/resolving Google Font metadata (google/mod.rs, google/font_fallback.rs). None of these occur during code generation; they all happen at the resolve stage of the build pipeline.

Using IssueStage::CodeGen was incorrect and caused these font issues to be grouped/sorted with code generation errors rather than resolution errors. The local-font counterpart (FontResolvingIssue in next_font/local/mod.rs) already correctly uses IssueStage::Resolve.

How?

Single-line fix: change IssueStage::CodeGen.cell() to IssueStage::Resolve.cell() in the stage() method of impl Issue for NextFontIssue.

[nextjs-bot]

Tests Passed

[codspeed-hq]

Merging this PR will not alter performance

✅ 17 untouched benchmarks
⏩ 3 skipped benchmarks¹

---

_{Comparing sokra/NextFontIssue-issue-stage (fdbfbfb) with canary (3d2bab2)}

Footnotes

1. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩