Fix compatibility with native PyUSB usb.core.Device.ctrl_transfer

[relic-se]

This update accounts for the difference in the implementation of usb.core.Device.ctrl_transfer between native PyUSB and CircuitPython. Tested on MacOS with Python 3.14 and Adafruit Fruit Jam with CircuitPython 10.

Related to adafruit/Adafruit_CircuitPython_USB_Host_Mouse#18

[tannewt]

What is the difference? Should we update CircuitPython so we can remove this in the future?

[relic-se]

What is the difference?

Native PyUSB uses the data_or_wLength parameter just to determine data length, and doesn't update the data of the bytearray. Instead, it returns an array.array object with typecode "B" and the corresponding data. Without this update, the data within the bytearray buffer remains all zeroes. The documentation of PyUSB isn't completely clear on this functionality, but this is what I could ascertain after some analysis.

Should we update CircuitPython so we can remove this in the future?

After reviewing the PyUSB library code (https://github.com/pyusb/pyusb/blob/a63c4f01df62a20bf35ce973ac4ba623d6a7693d/usb/core.py#L1057-L1108), the problem might be that we're using a bytearray rather than an array.array object. I should be able to get around to testing that theory later, but I don't have a strong opinion on the matter.

[relic-se]

@tannewt I've determined that using array.array does fix the issue in CPython and is still compatible with CircuitPython. I've updated this PR to use those objects instead of bytearrays, but I'm still casting back to bytearray in return statements. It's not exactly necessary to do this, but it keeps it consistent with the prior implementation.

[tannewt]

This is context about bytearray support too: pyusb/pyusb#489

[tannewt]

Ok, thanks!

[relic-se]

If proper bytearray support was added to PyUSB, it would likely make these changes unnecessary. I'll look into it at some point.