fix(ci): Fix failed device enumeration in CI

[peter-marcisovsky]

Description

Error log from repeatedly failing CI run:

Error log

Hard resetting via RTS pin...
2025-09-26 10:00:36 ERROR Failed Cases:
2025-09-26 10:00:36 ERROR   - Test USB Host async client (multi client)
FAILED
------------------------------ live log teardown -------------------------------
2025-09-26 10:00:36 INFO Created unity output junit report: /tmp/pytest-embedded/2025-09-26_09-59-08-434961/test_usb_host/dut.xml


=================================== FAILURES ===================================
________________________________ test_usb_host _________________________________
/usr/local/lib/python3.11/site-packages/pytest_embedded/plugin.py:1378: in pytest_runtest_call
    self._raise_dut_failed_cases_if_exists(duts)  # type: ignore
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
/usr/local/lib/python3.11/site-packages/pytest_embedded/plugin.py:1264: in _raise_dut_failed_cases_if_exists
    raise AssertionError('Unity test failed')
E   AssertionError: Unity test failed
------------------------------ Captured log setup ------------------------------
INFO     root:serial.py:110 Target: esp32p4, Port: /dev/ttyUSB0
------------------------------ Captured log call -------------------------------
WARNING  root:unity_tester.py:291 unity test case not found, probably due to a timeout. Assume the current test case is "Test USB Host async client (multi client)"
ERROR    root:plugin.py:1261 Failed Cases:
ERROR    root:plugin.py:1263   - Test USB Host async client (multi client)

Where the log from the failed test case shows no log:

Error log

2025-09-26 09:59:55 Press ENTER to see the list of tests.
2025-09-26 09:59:55 2
2025-09-26 09:59:55 Running Test USB Host async client (multi client)...
2025-09-26 09:59:55 USB Host installed
Hard resetting via RTS pin...
Hard resetting via RTS pin...
Hard resetting via RTS pin...
-------------------------------- live log call ---------------------------------
2025-09-26 10:00:24 WARNING unity test case not found, probably due to a timeout. Assume the current test case is "Test USB Host async client (multi client)"

Related

This might be connected with device not being correctly enumerated. Adding this check, for the CI run to trigger appropriate error, not just a timeout error.

Testing

---

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.