scripts/fwts_test: script now fails on aborted tests if desired. 
jobs/power-management.txt.in: jobs that depend on fwts_wakealarm to pass or
fail now fail on aborted test result. (LP: #1192684)
when failing on aborted, don't ignore critical and high failures as well.
Script is now able to detect USB Modem devices, and fixed the number of devices output
checkbox-old/checkbox/parsers/tests/udevadm_data: outputs collection
checkbox-old:parsers:udevadm: Added JSON ouput support

To be used by the corresponding entrypoint in plainbox and with the
command:

udevadm info --export-db | plainbox dev parse udevadm
checkbox-old:parsers:udevadm: Remove guess from device bus

They were causing devices without any product/vendor information,
aka Unknown:Unknown.
checkbox-old:parsers:udevadm: change how OTHER category works

Only accept devices with a valid product information.
checkbox-old:parsers:udevadm: Trust udev

Remove the code using capabilities bitmask check (for MOUSE and KEYBOARD),
udev does the same thing.
(See http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-input_id.c)

Added the following new categories:
TOUCHPAD, TOUCHSCREEN and ACCELEROMETER.
checkbox-old:parsers:udevadm: improve CAPTURE device detection

By filtering devices such as media/hot keys.
checkbox-old:parsers:udevadm: Improve WIRELESS device detection

To be valid a device needs a product name.
On arm based devices we can find it as a module in the platform modalias
of one of the parent devices.
checkbox-old:parsers:udevadm: Remove detection with RFKILL_TYPE

to avoid creating devices named hci0 for instance.
checkbox-old:parsers:udevadm: VIDEO ID_TYPE for non USB only

Several webcams have this property and we prefer to only get the CAPTURE
category.
Only use the ID_TYPE == VIDEO test for non-USB devices.
checkbox-old:parsers:udevadm: Detect rtsx CARDREADER

Several new models of Realtek card readers are using this driver.
checkbox-old:parsers:udevadm: Use the NAME key as a fallback.
checkbox-old:parsers:udevadm: BT, handle vendor specific class

Some Bluetooth devices belongs to the "vendor specific" (0xFF) USB class
and cannot be detected as Bluetooth devices because they're not using the
"0xE0" Wireless USB base class, e.g:

E: MODALIAS=usb:v04CAp2007d0112dcFFdsc01dp01icFFisc01ip01
(Broadcom Corp BCM43142A0)
Note that "Broadcom Corp" USB vendor_id is 0a5c, not 04ca.

To avoid a result where the category is set to Bluetooth but without a
product nor a vendor information, those fields are fetch from the first
parent providing ID_MODEL_ENC and ID_VENDOR_ENC.
checkbox-old:parsers:udevadm: Identify BT device with SUBSYSTEM
checkbox-old:parsers:udevadm: Use Input modealias

Find product_id/vendor_id fields in the input modalias
checkbox-old:parsers:udevadm: Force input bus to USB

When an input device is a child of a USB device, force the bus to be USB
in order to query the ubs.ids database for vendor_id/product_id.
checkbox-old:parsers:udevadm: Filter invalid input vendor_id

Many input devices have their vendor_id set to 0 or 1.
To avoid mismatch when looking at usb.ids database, force the vendor_id to
0x009 (unused in usb.ids and pci.ids)
checkbox-old:parsers:udevadm: Improve CARDREADER detection

USB sticks must be filtered (using DEVTYPE disk or partition) or if the
vendor fallback "Generic" comes with a product including one of the
following patterns:
- Mass
- Storage
- Disk