t_usbhid/check_hid_get_data has been failing since it existed, mark as such

Don't crash when the device's HID Report Descriptor Pops from an empty stack.

Add tests for HID Parser Pop-on-empty-stack bug.

Move libusbhid tests' Report Descriptors and Report Data to seperate file,
so future tests of the kernel HID functions can use them too.

reorganize constant test data

Move MY*_ATF_CHECK_EQ debugging helper macros to before all functions.

Teach hid_parse_usage_in_page() how to understand hex literals, in
addition to the usual table lookup.

Fix round-trip of hid_usage_in_page(hid_parse_usage_in_page()) when
the usage is a catch-all format string.

This should allow usbhidctl(1) to understand an item argument of
"Button:Button_65535".

Rework unsigned range test cases.

If the USB HID 1.11 spec is interperted to the letter, there's no such
thing as a unsigned Logical/Physical Minimum/Maximum. When the (signed)
Minimum is greater than the (signed) Maximum, it's a possibility that
the device is attempting to present unsigned report data.

Fix hid_get_data() for negative or 32-bit report data.

value debugging for the Logical/Physical range checks

tests for libusbhid (many of which fail)