fix: remove loader chain delimiters in module trace logs

[chenjiahan]

Summary

• Ensure consistent formatting by removing loader chain delimiters from module trace logs.
• Avoid duplicates and maintain the error marker in the output.

Before

After

Checklist

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

[netlify]

✅ Deploy Preview for rsbuild ready!

Name	Link
🔨 Latest commit	590b667
🔍 Latest deploy log	https://app.netlify.com/projects/rsbuild/deploys/692faa9a1b38270007f96a98
😎 Deploy Preview	https://deploy-preview-6686--rsbuild.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 67 (no change from production) Accessibility: 100 (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.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[Copilot]

Pull request overview

This PR addresses formatting inconsistencies in module trace logs by removing loader chain delimiters (e.g., !=!) from module paths and relocating the error marker (×) to the end of the trace output.

Key changes:

• Apply removeLoaderChainDelimiter to trace origins and error files to clean up module paths
• Add duplicate detection to prevent the error file from appearing twice in the trace
• Move the error marker from individual file lines to the end of the entire trace output

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.