transport: propagate hid devices descriptors

[mroz22]

With the old bridge going out of service, we are no longer able to work with very old Trezor HID devices. We are only able to detect them but no communication is possible.

To test this, you need an ancient device.

Features (126 bytes) {
    bootloader_hash: 32 bytes 0xc4c32539b4a025a8e753a4c46264285911a45fcb14f4718179e711b1ce990524,
    device_id: 'F7F53817FDC08323ECA22200',
    imported: False,
    initialized: True,
    label: 'My Trezor',
    major_version: 1,
    minor_version: 2,
    passphrase_protection: False,
    patch_version: 0,
    pin_protection: False,
    revision: 20 bytes 0xdf524b9f35fd5cdba14eaa2bf2d948e3dc75254a,
    vendor: 'bitcointrezor.com',
}

This PR unifies how these devices are communicated for both bridge and webusb transports.

• c8712c0 - transport now propagates descriptors even for hid devices to higher layers. connect then tries to work with these descriptors resulting into 'Unable to open device' error. which already results in creation of an 'Unreadable device'.
• 719aa39 - a couple of fixes were needed to make it behave the same way for node-bridge

While testing this for possible regressions I noticed a nasty bug that we might need to address before releasing node-bridge publically

Screenshots of how it looks like in trezor suite now. cc @martykan since he is now addressing this #12487, cc @Hannsek since we might need some designs/copy. Those bullet points are not very accurate.

[Hannsek]

The bullet points are changed in this comment.

[szymonlesisz]

we can get rid of code duplicates from enumetate and listen functions by passing all the devices here and do filterDevices before const loadedDevices = await Promise.all(

[mroz22]

cool, added as a new commit 5d893ee