Try find port type in parent device

[soiamsoNG]

for docker enviroment udev not run well for device add by --device
without ID_BUS like ID* property, but we still can try find the must info from its parent.

below is sample output from udevadm info -t /dev/ttyACM0

└─1-4:1.0
┆ P: /devices/pci0000:00/0000:00:02.1/0000:01:00.0/usb1/1-4/1-4:1.0
┆ E: DEVPATH=/devices/pci0000:00/0000:00:02.1/0000:01:00.0/usb1/1-4/1-4:1.0
┆ E: SUBSYSTEM=usb
┆ E: DEVTYPE=usb_interface
┆ E: DRIVER=cdc_acm
┆ E: PRODUCT=303a/1001/101
┆ E: TYPE=239/2/1
┆ E: INTERFACE=2/2/0
┆ E: MODALIAS=usb:v303Ap1001d0101dcEFdsc02dp01ic02isc02ip00in00
└─tty/ttyACM0
┆ P: /devices/pci0000:00/0000:00:02.1/0000:01:00.0/usb1/1-4/1-4:1.0/tty/ttyACM0
┆ M: ttyACM0
┆ R: 0
┆ U: tty
┆ D: c 166:0
┆ N: ttyACM0
┆ L: 0
┆ E: DEVPATH=/devices/pci0000:00/0000:00:02.1/0000:01:00.0/usb1/1-4/1-4:1.0/tty/ttyACM0
┆ E: SUBSYSTEM=tty
┆ E: DEVNAME=/dev/ttyACM0
┆ E: MAJOR=166
┆ E: MINOR=0

[RossSmyth]

I would highly recommend not bringing in regex for such an operation due to its extreme compilation weight & size cost.

[RossSmyth]

Review is tied with #201

[sirhcel]

Thank you for creating this PR @soiamsoNG! Looking at the MODALIAS strings is definitely something we can do for improving finding a certain device in a Docker environment.

I agree with @RossSmyth, that using the regex crate is - despite its convenience - on the heavy side. #168 contains measurements showing a significant reduction of built times for Windows by switching to regex-lite. We are currently also evaluating custom parsing of similar strings in #201 and it looks to me at a first glance that we have a good chance to get away with a much simpler parsing for MODALIAS strings than using regex or regex-lite.

Looking at file2alias.c from the Linux Kernel it looks like we might even get away without any regex magic at all. And we already got a regex-free proposal with #170 (comment).

[sirhcel]

Thank you @soiamsoNG and @RossSmyth for your contributions!