fix(ios): allow apps to override plugin Info.plist permission strings

[shanerbaner82]

Summary

• iOS plugin compiler used to silently skip Info.plist keys already present, so plugin manifest changes never reached the rendered plist on rebuild — no way to address App Store rejection emails asking for more explicit permission language without hand-editing nativephp/ios/NativePHP/Info.plist.
• It also meant when multiple plugins claim the same key (e.g. mobile-camera and mobile-scanner both set NSCameraUsageDescription), plugin order silently picked the winner with no app-level recourse.

What changed

• IOSPluginCompiler::injectPlistEntries now updates existing string/array values instead of skipping them. Plugin manifests stay the source of truth across rebuilds.
• New permissions block in config/nativephp.php. Anything set there is applied as the final layer after all plugins, giving the app developer the last word:

  'permissions' => [
      'NSCameraUsageDescription' => 'Used to take a profile photo.',
      'NSMicrophoneUsageDescription' => 'Used to record audio with your videos.',
  ],

• Replaced the test that locked in the skip behavior; added coverage for the app-level override path.

Android isn't included — its permission rationale is shown by app code at runtime, not declared in the manifest, so there's no equivalent to override.

Test plan

• vendor/bin/phpunit --filter "IOSCompilerTest|AndroidCompilerTest|PluginManifest|PluginRegistry|PluginDiscovery" — 90 tests pass
• Manual: in an app with conflicting plugins (mobile-camera + mobile-scanner), set NSCameraUsageDescription in config/nativephp.php permissions block, rebuild iOS, verify nativephp/ios/NativePHP/Info.plist and NativePHP-simulator-Info.plist both pick up the override.
• Manual: with no app-level override, verify the plugin's manifest value still lands (now updates on rebuild instead of going stale).

🤖 Generated with Claude Code