transport - fixes and more testing scenarios

[mroz22]

🐰 🕳️

Commits

• ca388c5 - to be able to use the already existing test for testing node-bridge too, we need to move the tests to transport-bridge package. The reason is that now these tests must import from both transport and transport-bridge package and transport-bridge is not dependency of transport package.
• 9d9e904 - cleanup in sessions background.
• 1fe634e - tests got adapted so that we can run them in 4 different setups (old/new, hw/emu). useful for detecting differences between implementations (there should be none) but the fact is that there are some at the moment, all of them documented here https://github.com/trezor/trezor-suite/blob/transport-meow/packages/transport-bridge/e2e/expect.ts#L1-L2
• d37cc1c - CI now runs both emulator variants of the transport-birdge tests. I also made some changes in setup to make the tests faster. I believe that running jest test runner in a dedicated container is not necessary since they may be easily run in the base container. It saves maybe 2 minutes or so.
• 606203b - this only renames events.test.ts to multi-client.test.ts because this test is indeed focusing on how TransportBridge class is behaving in this scenario.
• 0eeb8e6 - this commit adds a new test documenting incorrect behavior of node-bridge in cases of concurrent enumeration. I believe that this issue comes from node USB lib or possibly from the underlying os USB drivers.
• 582b299 - solution for the issue documented in the prev commit. we simply run enumeration in sequence one by one with the help of sessions background.
• 7473ced - disabling unrelated test, issue created connect-popup: tests setup - changes in sharedworker impossible #13762
• 83873b8 - /read endpoint should not parse body as JSON as added in Chore/transport bridge types #13592.

Follow-ups:

• finish webusb tester test(transport-test): add webusb tester build #13769
• finish/review PR by @szymonlesisz Fix/transport usb abort #13570
• add path masking as done in the old bridge, to get rid of differences documented in https://github.com/trezor/trezor-suite/blob/transport-meow/packages/transport-bridge/e2e/expect.ts#L1-L2
• there is still one possible racecondition similar to the one fixed in 582b299. The same async code execution might be triggered in onconnect event here https://github.com/trezor/trezor-suite/blob/develop/packages/transport/src/api/usb.ts#L50

Issues:

• discovery - labeling - apps synchronization #13550 was found while testing this.
• node-bridge "Segmentation fault: 11" #12163 (comment) is addressed by this.

[szymonlesisz]

all 4 tests are passing on my machine