BLED112 connection blocks if the device do not send right GATT table

It would be better to add a timeout, because when it happens, we have to kill the process.

This issue should not happen normally, but during my tests to add peripheral commands to baBLE, I noticed this error when I was not able to answer to a service/characteristic probe (ReadByGroupType or FindInformation HCI commands).

Start by tracing the BLED112 connection flow around the ReadByGroupType and FindInformation HCI probes. Reproduce the case where the device does not answer a service or characteristic probe, then identify the connection wait that needs a timeout. Done means the process no longer blocks indefinitely when the GATT table response is missing.

Written by the indexing model from the issue text.