Add @try/@catch exception guards to iOS TurboModule bridge

[NickSxti]

Summary

• Add @try/@catch exception guards to all TurboModule bridge methods in RNQonversion.mm and RNNoCodes.mm
• Prevents NSExceptions from reaching RCTTurboModule.mm's performVoidMethodInvocation, which rethrows them as C++ exceptions causing std::terminate → SIGABRT on React Native New Architecture
• Promise methods: caught exceptions are surfaced via reject("QONBridgeException", ...)
• Void methods & delegate callbacks: caught exceptions are logged via NSLog
• dispatch_async blocks (NoCodes showScreen/close): guards placed inside the block to catch exceptions on the main queue

Fixes #421
Upstream RN bug: facebook/react-native#54859
Linear: DEV-637

Test plan

• iOS build succeeds locally (example app, Debug, iphonesimulator)
• Manual test: inject @throw in an impl method → verify crash is caught and logged, not fatal
• Verify on New Architecture (newArchEnabled: true)
• Verify on Old Architecture (newArchEnabled: false) — no regressions

🤖 Generated with Claude Code

[NickSxti]

Local verification

Build: BUILD SUCCEEDED — iPhone 16 Pro simulator, iOS 18.3.1
Runtime: App launched and ran without crashes (confirmed process alive via launchctl + ps)
Logs: No NSException, SIGABRT, or QONBridgeException in simulator logs — normal operation path unaffected

Code review notes

• Only 2 files changed: RNQonversion.mm and RNNoCodes.mm
• Pattern is consistent:
  • Promise methods → @try/@catch with reject("QONBridgeException", ...)
  • Void methods → @try/@catch with NSLog
  • Delegate callbacks → @try/@catch with NSLog
  • dispatch_async blocks → guard placed inside the block
• Normal SandwichError → reject() flow is not affected — @catch only catches NSException

Screenshot: