The different hardware DPDK supports is not homogeneous and support a variety
of different features. A user-friendly solution would probe the hardware under
test and skip all test cases that cannot be executed due to missing features.

There are multiple dimensions to this task.
1. Device probing. We can leverage existing DPDK probing capabilities in a DPDK
app. A machine-readable output format must be defined, such as json. The fields
themselves must be well-defined.
2. Test case/suite marking with required capabilities. If a test case isn't
marked, it should run on all hardware. There could be different names for the
same feature across different hardware, in which case we should decide whether
we want to merge these under one DTS-defined name or we'll mark each test
case/suite with multiple names.