ci(usb_host): Class drivers test apps run on esp32p4

[peter-marcisovsky]

Description

This MR enables class drivers test apps, to be run on esp32p4

Changes

• New esp32p4 usb_host target runner BrnoVM0114 was added to the CI
• Enabled test apps build and run in CI for esp32p4
• Memory leak checks evaluation during test case teardown updated to new API
• removed all code in test apps related to IDF versions lower than 5.0
• usb_host_lib_set_root_port_power function used to toggle connection of USB devices must be used for esp32p4, but has been implemented only in IDF 5.2
  • for IDF versions lower than 5.3, the old way of connection toggling (using PHY) is used, because esp32p4 has been added from IDF 5.3
  • for IDF versions higher than, including 5.3, the new way of connection toggling (using root power) is used.

Related

• RDT-995 Add new esp32p4 usb_host runner
• IDF-11346 Build USB P4 runners for GitHub
• IDF-11685 Run esp-usb class driver tests in CI on esp32p4
• Follow up: Enable target run for esp32p4 on IDF 5.3 once the IDF 5.3 docker image is updated

Testing

• CDC-ACM, HID, MSC, UVC class driver tests are passing locally on a reproduced CI target runner setup
• UAC class driver not modified, since it's not being run in any CI tests

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.

[peter-marcisovsky]

CI build failed: usb_host_lib_set_root_port_power function used for trigger connection/disconnection in target tests not present in IDF 5.0 and IDF 5.1

[peter-marcisovsky]

CI tests passed on the current esp32s2 target runners, waiting for the new esp32p4 target runners to be build and the CI tests to be run on them.

[tore-espressif]

@peter-marcisovsky The P4 tests passed, thank you!

The failure on release/v5.3 should be already fixed. We must wait for new release/v5.3 docker image release (or ignore the 5.3 tests for now)