Implement characteristic instance id support

[rohitsangwan01]

This Pr is not stable,
Tried adding Instance Id support, so that we can define multiple chars with same uuid in same service, and identify those with instanceId

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 4 🔵🔵🔵🔵⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Race Condition The subscribedCharDevicesMap is accessed from multiple threads without proper synchronization, which could lead to race conditions when handling device subscriptions and notifications. private val subscribedCharDevicesMap: MutableMap<String, MutableList<BluetoothGattCharacteristic>> = HashMap() Memory Leak The bluetoothGattCharacteristics list grows indefinitely as characteristics are added, without any cleanup mechanism when services are removed. private val bluetoothGattCharacteristics: MutableList<BleCharCache> = mutableListOf() Error Handling The findCharacteristic method could return null without proper error handling in the calling code, potentially leading to null pointer exceptions. fun String.findCharacteristic(instanceId: Long?): BluetoothGattCharacteristic? { if (instanceId != null) { return bluetoothGattCharacteristics.find { it.uuid == this && instanceId.toInt() == it.instanceId }?.char } return bluetoothGattCharacteristics.find { it.uuid == this }?.char }

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Add thread synchronization Add synchronized block around bluetoothGattCharacteristics list modifications to prevent potential concurrent modification issues android/src/main/kotlin/com/rohit/ble_peripheral/BleExtension.kt [93-94] -bluetoothGattCharacteristics.add(BleCharCache(uuid, instanceId.toInt(), char)) +synchronized(bluetoothGattCharacteristics) { + bluetoothGattCharacteristics.add(BleCharCache(uuid, instanceId.toInt(), char)) +} Apply this suggestion Suggestion importance[1-10]: 8 Why: The suggestion prevents potential race conditions and data corruption by adding thread synchronization around shared list modifications, which is crucial for thread safety in a BLE implementation.	8
	Add null safety check Add null check before accessing device.name to avoid potential NullPointerException when device name is not available android/src/main/kotlin/com/rohit/ble_peripheral/BlePeripheralPlugin.kt [486-492] bleCallback?.onCharacteristicSubscriptionChange( it, - characteristicId, + characteristicId, isSubscribed, - device.name, + device.name?.toString(), instanceIdArg = descriptor.characteristic.instanceId.toGivenInstanceId() ) {} Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion addresses a potential NullPointerException by adding a null safety check for device.name, which is important for app stability and crash prevention.	7