fix(core): preserve Hermes internal bytecode frames in Expo

[Trancever]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

Preserve Hermes InternalBytecode.js frames as app:///InternalBytecode.js with in_app: false before Expo rewrites JavaScript filenames to the application bundle. Recognize both bare and slash-prefixed filenames after path normalization.

💡 Motivation and Context

Follow-up to #3348 and #3518. The existing exclusion runs after Expo's early returns and only matches /InternalBytecode.js. Hermes promise helpers can therefore be attributed to the application bundle, causing invalid source-map lookups and incorrect grouping of unrelated errors.

💚 How did you test it?

• Reproduced the incorrect filename and in_app values with a failing test before applying the fix.
• Added 12 regression cases: iOS/Android, Expo/non-Expo, and bare/slash-prefixed/absolute Hermes filenames. Each verifies runtime, application, and native frames together.

📝 Checklist

• I added tests to verify changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed. (Changelog updated.)
• I updated the wizard if needed. (Not applicable.)
• All tests passing.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec. (Not applicable: no public API change.)
• No breaking changes.

🔮 Next steps

🚨 PR created with AI assistance, but it was carefully reviewed by Dweet team where this patch is already used on prod in an Expo app.

[alwx]

Thanks for your PR, @Trancever! One small thing left before I merge it.

[alwx]

Thanks for your contribution, @Trancever!