fix(): prevent iOS startup hang while loading protocol modules

[PeratX]

Summary

• make early JavaScript results and waiter registration atomic within one actor
• preserve results that arrive before awaitResultWithID(_:) registers its continuation
• restrict StatusBar.setBackgroundColor to Android, where the Capacitor API is implemented

Root cause

iOS protocol-module loading evaluates JavaScript and then awaits a result by ID. The existing implementation split result storage and listener registration across two actors. A JavaScript result could arrive after the result lookup but before the waiter was registered. The notification then removed the listener entry, and the late continuation was never resumed, leaving startup permanently waiting on the native launch screen.

The reported Error: not implemented message came from calling the Android-only status-bar background-color API on iOS. It occurs after protocol initialization and was not the cause of the startup hang, but this PR removes that unrelated error as well.

Validation

• reproduced with the latest App Store client, version 3.34.4, on an iPhone 7 Plus running iOS 15.8.5
  • 15 of 20 launches remained on the native launch screen after four seconds
  • one affected launch was still stuck after an additional 30 seconds
• built and installed the patched v3.34.4 source under a separate bundle identifier so the existing app and data were not overwritten
• completed initial setup and launched the patched build successfully 5 consecutive times on the same physical device
• passed 50,000 result-before-wait, wait-before-result, and concurrent actor interleavings
• passed the production Angular build, Capacitor iOS sync, and complete arm64 iOS build

References #218

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud