fix(darwin): add DidFailToConnectPeripheral handler

[acouvreur]

When using the Connect on peripherals with an unstable state, I've found that it might be because of the missing DidFailToConnectPeripheral handler (https://developer.apple.com/documentation/corebluetooth/cbcentralmanagerdelegate/centralmanager(_:didfailtoconnect:error:)?language=objc)

After successfully establishing a local connection to a peripheral, the central manager object calls the centralManager:didConnectPeripheral: method of its delegate object. If the connection attempt fails, the central manager object calls the centralManager:didFailToConnectPeripheral:error: method of its delegate object instead. Attempts to connect to a peripheral don’t time out. To explicitly cancel a pending connection to a peripheral, call the cancelPeripheralConnection: method. Deallocating peripheral also implicitly calls cancelPeripheralConnection:.

So this should properly handle the connection failed event.

Note:

I would like to be able to use that error object. However, it requires to completely change the channel type.

I might do another PR later.

[deadprogram]

Is there any way to test this out @acouvreur?

[acouvreur]

Is there any way to test this out @acouvreur?

Rare cases when you connect to a device and it fails for some reason, like you were too far from the device but close enough to get signal.

Based on CoreBluetooth documentation, it is clear to me that we need this handler in case of error, because right now only the happy path is implemented.