fix(dcd): Fixed race condition on device disconnect

[tore-espressif]

TinyUSB does not provide any locking means to protect the DCD variables. This can lead to race conditions when the user is trying to submit a transfer while the device is being disconnected. This can cause the device to be in an inconsistent state, leading to a crash or undefined behavior.

This commit adds a spin-lock to protect the DCD variables during device disconnect.

• Reported in crash in tud_hid_keyboard_report() due to race condition (IDFGH-8198) espressif/esp-idf#9691
• Also reported in fix(tusb_msc): Cache sector metrics, enable storage buffering espressif/esp-usb#131
• Merged in espressif fork fix(dcd): Fixed race condition on device disconnect espressif/tinyusb#55

[hathach]

can we use the osal_mutex instead https://github.com/hathach/tinyusb/blob/master/src/osal/osal_freertos.h#L152, there is an osal API for that ?

[tore-espressif]

can we use the osal_mutex instead https://github.com/hathach/tinyusb/blob/master/src/osal/osal_freertos.h#L152, there is an osal API for that ?

I decided for critical section instead of OS primitives because many of these sections are in ISRs

• ISR must not block. So calling osal_mutex_lock() is not acceptable
• With critical section we get minimal latency and overhead
• Intention and simplicity: We really just need an atomic access to xfer_ctl_t.