feature(esp_tinyusb): Added tusb_teardown() call while tinyusb_driver_uninstall()

[roma-jam]

esp_tinyusb (Not a Release)

Requirements

• To uninstall tinyusb driver, a teardown tinyusb stack should be called. (https://github.com/espressif/tinyusb/pull/27)

Description

• Added tusb_teardown() call while tinyusb_driver_uninstall()
• Added test case to verify reconfiguration procedure

Changes

• Added tusb_teardown()
• Added test case device_class_reconfiguration which:
  1. Configure tinyusb driver with HID class
  2. Install tinyusb driver
  3. Wait connection event (which means the enumeration completed successufully)
  4. Uninstall tinyusb driver
  5. Repeat steps 1-4 for next classes [CDC, MSC]

Notes

1. Test case only covers the enumeration and configuration for a class. There is no communication in between tinyusb driver tinyusb_driver_install() and tinyusb_driver_uninstall() calls.

Resolve https://github.com/espressif/esp-idf/issues/13788

[roma-jam]

@tore-espressif , @peter-marcisovsky This changes unlock the possibility to run usb device tests one by one (https://github.com/espressif/tinyusb/pull/27 should be merged first, though).

I posted two questions for both of you, because it seems that we can make it better and we can use it.

I need that for enumeration driver testing (but maybe I will eliminate esp_tinyusb component from the chain, but anyway), so feel free to check it out when possible.

Meanwhile, I will go and cover the Enum Driver as much as I can.