Correct handling of USB3Vision control endpoints

[27Cobalter]

Fixes #500

This change removes the incorrect assumption that endpoint_in == (endpoint_out | LIBUSB_ENDPOINT_IN). This was causing issues with cameras like the Toshiba-Teli BU406M (where OUT=0x01 but IN=0x82).

Summary of changes:

• Stored control OUT and IN endpoints in separate variables with their raw values.
• Removed the manual bitwise OR flag logic.
• Updated log messages to show both endpoints in 2-digit hex format (consistent with libusb style).

[Copilot]

Pull request overview

This PR fixes a critical bug in USB3Vision control endpoint handling that prevented certain cameras (like the Toshiba-Teli BU406M/BU505MG) from working correctly.

Changes:

• Separated control endpoint storage into distinct IN and OUT fields with raw endpoint addresses
• Removed incorrect assumption that IN endpoint could be derived from OUT endpoint using bitwise OR
• Updated endpoint selection logic to use stored values directly based on transfer direction

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[EmmanuelP]

Thanks @27Cobalter