fix(diagnostic): improve diagnostics for swc wasm plugins when mismatch

[SyMind]

Summary

improve diagnostics when wasm plugin binary format mismatch

Checklist

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

[netlify]

✅ Deploy Preview for rspack ready!

Name	Link
🔨 Latest commit	4ab5522
🔍 Latest deploy log	https://app.netlify.com/sites/rspack/deploys/670c5c75b501f8000834870f
😎 Deploy Preview	https://deploy-preview-8001--rspack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[h-a-n-a]

What is the context?
cc @hardfist @chenjiahan

[chenjiahan]

I think the motivation for this PR is to add the test case back, @SyMind right?

[chenjiahan]

We can change the PR title to make it more accurate.

[SyMind]

@hardfist let me revert this PR. Initially, I thought swc converted panics into Result, which would allow us to modify the error handling. However, after reviewing the swc code, I found that no such change has been made.

Therefore, I believe I misunderstood the purpose of this PR. We need @hardfist to take a look at it.

[hardfist]

What is the context? cc @hardfist @chenjiahan

swc support throw error when wasm binary not match now, so it's safe to add this test case back without enabling catch_on_unwind
https://github.com/swc-project/swc/pull/9562/files#diff-4d01e730818bcc35a17d65dd364390283fd29e3fb1dc0e35050a67034eeb474dR111

another block in swc side https://github.com/swc-project/swc/blob/main/crates/swc/src/plugin.rs#L169, we need to remove the panic here first