connect: initialize should be able to timeout

[mroz22]

This is a heavy draft, to be discussed with @marekrjpolak first and szymonlesisz later

• it is possible to get the device into a state where it can't be worked with. It is enumerated but any attempts to open it or to write it will remain hanging forever. see video:

vide0.mov

I am able to reproduce this behavior through "uncooperative acquire". 1 instance of suite is doing discovery, another instance steals session. We should I am at fixing the root of the problem as well of course but on the other hand - some of the calls to the device should be timeout-able. This is something I would like to discuss with @marekrjpolak what is the right place to do this.

In the meantime I would probably add this little bandaid to fix a case where Suite stays hanged without any clear communication about what is happening.

There are possibly controversial commits:

• 50191b4 - suite reducers did not accept change from unacquired to unreadable.
• 717a857 - the band aid
• e3446af - promises clearing to be discussed.

After all the changes it looks like this:

vide1.mov

related

• transport: propagate hid devices descriptors #13220 handling of unreadable devices when they are connected