MSC driver assertion failure. IN and OUT endpoints callback ordering issue

Sometimes the MSC driver would hit the `util_assert()` here:
https://github.com/ARMmbed/DAPLink/blob/main/source/usb/msc/usbd_msc.c#L1087

The MSC driver expects its `ReadEP()` and `WriteEP()` sequence has the same order as the `BULKOUT_Event` and `BULKIN_Event` sequence. But dependent on how the usb driver implements the handler, even if MSC driver does `ReadEP()` before `WriteEP()`, the usb driver may handle`BULKIN_Event` and triggers the `util_assert`

What do you think about this issue ? Should this ordering issue be handled in the USB driver or the MSC driver ?

Start at source/usb/msc/usbd_msc.c:1087 and trace the MSC ReadEP() and WriteEP() calls alongside BULKOUT_Event and BULKIN_Event handling. Compare the ordering guarantees provided by the USB driver and MSC driver; done means deciding which layer owns the ordering and preventing the util_assert() failure under the affected callback sequence.

Written by the indexing model from the issue text.