Floss: Add InformationalRule to hcidoc

This prints peer device's names and also the ACL connection stats,
e.g. time and direction.

Here are some example output of this rule in action selected from
several random snoop logs, address redacted.
xx:xx:xx:xx:E8:D8 (BR/EDR, 企鵝love小羊), 0 connections
xx:xx:xx:xx:7D:E8 (Dual, Chromebox for Meetings), 0 connections
xx:xx:xx:xx:75:DB (LE, {"N00Z6", "BCM4350C0 UART 37.4 MHz"}), 0 connections
xx:xx:xx:xx:26:8E (BR/EDR, RASPI_AUDIO), 0 connections
xx:xx:xx:xx:C7:8A (LE, LE-Acrux), 0 connections
xx:xx:xx:xx:29:B1 (LE, LE_WH-1000XM4), 0 connections
xx:xx:xx:xx:CF:F1 (BR/EDR, WH-1000XM4), 1 connections
> Handle: 256, Host initiated, 07:46:48.714164 to N/A
xx:xx:xx:xx:05:EC (Dual, {"LE-Ketan Bose NC 700", "Ketan Bose NC 700"}), 1 connections
> Handle: 51, Host initiated, 13:29:33.661278 to 13:34:08.093888
xx:xx:xx:xx:B4:25 (LE, <Unknown name>), 3 connections
> Handle: 3585, Host initiated, 15:29:21.098920 to N/A
> Handle: 3585, Host initiated, 15:47:22.142535 to 15:47:22.275464
> Handle: 3585, Host initiated, 15:47:22.301486 to N/A

It's better if we can drill further to profile level but that needs
some modification on packetgen for acl_packets, so let's separate
the effort.

Bug: 288211078
Tag: #floss
Test: Use hcidoc with random btsnoop logs from feedback reports.
Change-Id: Ie20e1c0f22a0e24acff88cbfe70a179098965bee