fix: prioritize custom file path in error logs

[chenjiahan]

Summary

Checks for stats.file first before falling back to stats.moduleName for better error reporting. This ensures custom file paths take precedence over module names when available.

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for rsbuild ready!

Name	Link
🔨 Latest commit	383b4fe
🔍 Latest deploy log	https://app.netlify.com/projects/rsbuild/deploys/68da279ca3dc9b0008bdae9d
😎 Deploy Preview	https://deploy-preview-6281--rsbuild.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 69 (🔴 down 9 from production) Accessibility: 97 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 60 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull Request Overview

This PR refactors the file name resolution logic in error reporting to prioritize custom file paths over module names. The change ensures that when both stats.file and stats.moduleName are available, the custom file path is used first for better error reporting clarity.

• Reorders the priority of file path resolution to check stats.file before stats.moduleName
• Consolidates the file resolution logic into a single variable assignment
• Removes the fallback logic that previously checked stats.file last

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}