chore: use LiveKitWebRTC

[griffithcaleb]

Switch iOS dependency from WebRTC-SDK to LiveKitWebRTC to resolve CocoaPods framework conflicts

Problem

When using livekit-react-native-webrtc alongside other WebRTC-based SDKs pod install fails with:

[!] The 'Pods-XYZ' target has frameworks with conflicting names: webrtc.xcframework.

Both WebRTC-SDK and JitsiWebRTC vendor a framework named webrtc.xcframework, and CocoaPods refuses to integrate two frameworks with the same filename into the same target.

Related: livekit/livekit#2809

Solution

Switch the iOS CocoaPods dependency from WebRTC-SDK to LiveKitWebRTC — LiveKit's own repackaged WebRTC build from livekit/webrtc-xcframework. This is the same WebRTC codebase (same version 144.7559.10) but:

• Vendored as LiveKitWebRTC.xcframework (no filename collision)
• Objective-C symbols are prefixed with LK (e.g., RTCPeerConnection → LKRTCPeerConnection, no linker-level collisions)

This matches what client-sdk-swift already does — it depends on LiveKitWebRTC, not WebRTC-SDK.

Changes

• Podspec: WebRTC-SDK → LiveKitWebRTC dependency
• All ios/ ObjC sources:
  • #import <WebRTC/...> → #import <LiveKitWebRTC/...>
  • #import <LiveKitWebRTC/WebRTC.h> → #import <LiveKitWebRTC/LiveKitWebRTC.h> (umbrella header renamed)
  • All WebRTC SDK type references prefixed with LK (e.g., RTCPeerConnection → LKRTCPeerConnection)
  • Header filenames in imports unchanged (LiveKitWebRTC keeps original header filenames)
  • Locally-defined types preserved (RTCVideoView, RTCVideoViewManager, RTCVideoViewObjectFit) to maintain JS bridge compatibility

No JS-side changes required

The native module name (WebRTCModule) and native view name (RTCVideoView) are unchanged, so no changes to the TypeScript/JavaScript layer are needed.

[griffithcaleb]

Believe CI is failing becase consuming test app needs to declare livekit podspec repo