init: Fixing indent
init: Adding LLDP support to init

This patch is one the serie to get LLDP information being reported by eDeploy.

This patch is making the lldp service running and waits until the lldp
status is reported as ok.

It will wait up to 45 seconds to get this LLDP report being done.

As the LLDP is started at the same time as the nic configuration, we
have a good chance the NIC will have received some LLDP packets during
the DHCP requests.
detect: Reporting current LLDP configuration per interface

When detecting the hardware, let's report what is the LLDP information
reported by the switch.

It is now possible to match some hardware based of its low-level network configuration (port location, switch name, available VLANs, ...)

The reported information are really depending from the switch model/version and its configuration.
This patch will report everything found from the "lldaptool -n -t -i <interface>" output under the following format:
    'lldp', '<nic_name>', 'header, 'value'

The default parsing of lldaptool is turned into a 2 field reporting.
If multiple levels are found, they will be turned into "x/y" format in the header.

A typical output looks like:
 ('lldp', 'eth3', 'Chassis ID/MAC', 'f8:b1:56:15:e6:c6'),
 ('lldp', 'eth3', 'Port ID/Ifname', 'gi3_4'),
 ('lldp', 'eth3', 'Time to Live', '120'),
 ('lldp', 'eth3', 'MAC_PHY Configuration Status', 'Auto-negotiation supported and enabled'),
 ('lldp', 'eth3', 'MAC_PHY Configuration Status/PMD auto-negotiation capabilities', '0x6c01'),
 ('lldp', 'eth3', 'MAC_PHY Configuration Status/PMD auto-negotiation capabilities/MAU type', '1000 BaseTFD'),
 ('lldp', 'eth3', 'Port Description', 'gigabitethernet3_4'),
 ('lldp', 'eth3', 'System Name', 'Switch POD'),
 ('lldp', 'eth3', 'System Description', 'R1-2401 VRTX 1Gb Switch Module'),
 ('lldp', 'eth3', 'System Capabilities/System capabilities', ' Bridge'),
 ('lldp', 'eth3', 'System Capabilities/System capabilities/Enabled capabilities', 'Bridge'),
detect: Adding test code for lldp parsing

As the output could be weird, let's add some code to handle the
testability of it