Use PointerVector to manage devices in DeviceLists.

[Dimi1010]

Rework of #1431 p1 and p2.

• Refactored to use PointerVector<Device> in lists:

  • PcapLiveDeviceList - provides a better API then std::vector<std::unique_ptr<Device>>
  • PcapRemoteDeviceList - provides an automatic memory management then std::vector<Device*>
  • PfRingDeviceList - provides a better API then std::vector<std::unique_ptr<Device>>

• Added begin/end iteration API to lists:

  • PcapLiveDeviceList
  • PfRingDeviceList

• Added iterator and const_iterator type aliases to the lists.
  IMO, the member type definitions should follow the standard member types, even if they slightly deviate from the internal library convention as that would allow better integration with standard templated utility functions and classes.
  
  In addition, I feel like the names PcapRemoteDeviceIterator and PcapConstRemoteDeviceIterator should be best left to concrete definitions of custom iterator classes if needed, instead of being member type alias definitions. Part of the point of the member type alias definitions is to allow templated functions to dynamically fetch the type of the container at compile time, and for that the definition member identifier needs to be consistent across different containers.
  Affected lists:

  • PcapLiveDeviceList
  • PcapRemoteDeviceList
  • PfRingDeviceList

• Deprecated getPcap*DevicesList.
  The list classes should provide direct functions for iteration and fetching devices. It makes no sense to have to get another 'List' from a 'List' class. Additionally this getter in particular returns a reference which ties the internal implementation to it making it difficult to change.
  Affected Lists:

  • PcapLiveDeviceList
  • PfRingDeviceList

• Updated usages of deprecated methods in the library with non-deprecated methods.

[tigercosmos]

LGTM

[Dimi1010]

@tigercosmos added PfRingDeviceList to the refactor last minute. Sry for the re-review request.