fix: iOS physical device code signing for SPM-based OpenSSL.framework

[boorad]

Fixes #857

This PR resolves the code signing error 0xe8008015 that prevents react-native-quick-crypto from running on physical iOS devices when using Swift Package Manager for OpenSSL integration.

Root cause: The existing build phases used --preserve-metadata=identifier,entitlements which conflicts with pre-signed xcframeworks from SPM. Additionally, || true was silently suppressing codesign failures.

Solution: Created a reusable helper script (scripts/quickcrypto_spm_fix.rb) that library consumers add to their Podfile. The script:

• Uses --force --deep --timestamp=none to properly strip and re-sign the framework with the app's identity
• Adds chmod -R u+w to handle read-only framework copies from rsync
• Removes duplicate/conflicting embed phases that accumulate across pod installs
• Positions the embed phase at the end of build phases for correct ordering

Usage: Add to your Podfile:

require_relative '../node_modules/react-native-quick-crypto/scripts/quickcrypto_spm_fix'

post_install do |installer|
  react_native_post_install(installer)
  quickcrypto_fix_spm_signing(installer)
end

Also may help #844 & #851 

[boorad]

iPhone 11 physical device, showing off signed OpenSSL framework

[github-actions]

🤖 End-to-End Test Results - Android

Status: ✅ Passed
Platform: Android
Run: 20176284423

📸 Final Test Screenshot

Screenshot automatically captured from End-to-End tests and will expire in 30 days

---

This comment is automatically updated on each test run.

[github-actions]

🤖 End-to-End Test Results - iOS

Status: ✅ Passed
Platform: iOS
Run: 20176284436

📸 Final Test Screenshot

Screenshot automatically captured from End-to-End tests and will expire in 30 days

---

This comment is automatically updated on each test run.