Collect and report more information from real interfaces for debugging purpose

[DUFOUR Olivier]

For the sake of building more in-depth reports, especially on the network side, since many issues can be the root cause of a lot of trouble. Collecting more information about the involved network interfaces from the server hosting the test can help greatly.

It would be helpful to retrieve the following information :
1) in the case of a bond, or a bridge, or both at the same time, retrieve the real slave interfaces
This needs to take in account both linux bridges and OVS bridges, since MAAS allows both of them to be configured.
2) retrieve the PCIe address of the daughter interface, can helpful to notice cross-physical card bonding
3) retrieve the NIC model
4) retrieve the current module and its version used by the interface
5) get the type of the link
  this includes also on checking sensitivity if use fiber optics

This can potentially be associated with the run-iperf action with a supplementary option to enable the output.

As a bonus, it may be useful to check the packet error counters to detect any physical issue on the real interfaces

[Samuel Allan (samuelallan)]

If this is being worked on soon, please note that the magpie charm has a rewrite patch ready for review at https://review.opendev.org/c/openstack/charm-magpie/+/897648 . The rewrite changes a lot of things about the magpie charm and brings the codebase up to date. Please consider using the rewrite as a base for this, and/or reviewing the rewrite design. :) The design aims to make it easier to expand the action results for gathering and reporting on more information as requested in this bug.

[Francesco De Simone (fdesi)]

Thank you, Samuel.
Adding PR url: https://review.opendev.org/c/openstack/charm-magpie/+/911001