Security: Verbose Logging of Sensitive Audio Data (#438)

## Summary

Security: Verbose Logging of Sensitive Audio Data

## Problem

**Severity**: `Medium` | **File**:
`ios/audio/AudioSinkRenderer.swift:L17`

The `AudioSinkRenderer` logs the base64 encoded audio data, its length,
and other metadata using `NSLog`. This verbose logging can expose
sensitive audio stream data in the device's console logs, which could be
intercepted by other processes or during debugging sessions.

## Solution

Remove the `NSLog` statements that print the audio data payload and its
length. If logging is necessary for debugging, use a conditional debug
flag and avoid logging raw data payloads.

## Changes

- `ios/audio/AudioSinkRenderer.swift` (modified)

Signed-off-by: tomaioo <203048277+tomaioo@users.noreply.github.com>

Author: tomaioo

ios/audio/AudioSinkRenderer.swift

@@ -24,11 +24,6 @@ public class AudioSinkRenderer: BaseAudioSinkRenderer {
         let length = Int(pcmBuffer.frameCapacity * pcmBuffer.format.streamDescription.pointee.mBytesPerFrame)
         let data = NSData(bytes: channels[0], length: length)
         let base64 = data.base64EncodedString()
-        NSLog("AUDIO DATA!!!!")
-        NSLog("\(data.length)")
-        NSLog(base64)
-        NSLog("\(base64.count)")
-        NSLog("\(length)")
         eventEmitter.sendEvent(withName: LKEvents.kEventAudioData, body: [
             "data": base64,
             "id": reactTag