1.9.0: Improved physical drive reporting

Features:

• extend reported drive details on --detailed #140
  from:

  [CRITICAL]: Physical Drive NonRAID Solid State Disk 0:1:0 (Dell Ent NVMe CM6 MU 1.6TB / SSD / PCIe) 1599.74GiB status: CRITICAL
  [OK]: Physical Drive TOSHIBA KPM51MUG800G (0) (KPM51MUG800G / SSD / SAS) 800.17GiB status: OK
  [OK]: Physical Drive (2I:1:6) 240GB status: OK
  

  to:

  [CRITICAL]: Physical Drive NonRAID Solid State Disk 0:1:0 Failure predicted: True (Dell Ent NVMe CM6 MU 1.6TB, SSD, PCIe, Media life left: 100%, Status: Enabled) 1599.74GiB status: CRITICAL
  [OK]: Physical Drive TOSHIBA KPM51MUG800G (0) (KPM51MUG800G, SSD, SAS, Media life left: 100%, Status: Enabled, Hours on: 181) 800.17GiB status: OK
  [OK]: Physical Drive (2I:1:6, VK000240GWSRQ, SSD, SATA, Media life left: 89%, Status: Enabled, Hours on: 19415) 240.06GiB status: OK
  

• add physical driver performance data (temp, power on hours, media lifetime left) #142
• add warning/critical if physical drive media life time gets below certain values #143

Bugfixes:

• fixes issue with reported memory status on detailed view if all modules reported OK but memory subsystem had an issue #141
• fixes issue with disabled drives on Cisco servers #144

Possible breaking changes

Using --warning and --critical values for --mel and --storage at the same time will cause issues as these apply to both checks.

Thanks to @HHerrgesell for the contributions