Check RTE flow API rules implying RSS actions

Make sure that RTE flow API RSS action is carried out correctly

The test affirms that RSS flow action has proper effect on ingress traffic

Determine Rx settings based on the flow rule
Arrange a handful of Rx queues
Prepare TEST_ETHDEV_INITIALIZED state
Check maximum number of Rx queues
Enable isolated mode if need be
Query global RSS key and RSS HF if need be
- Prepare TEST_ETHDEV_CONFIGURED state
- Set device state to dummy value to allow to reconfigure device with the new MQ mode. This is acceptable because device configure API may be called multiple times.
Prepare TEST_ETHDEV_STARTED state
Change destination MAC to NIC MAC if it is present in pattern and promiscuous is disabled
Validate and create flow_rule_rss
Produce a template to generate traffic expected by the flow rule
Enable promiscuous mode if need be
Ensure that interface is UP on Tester side
Generate traffic and obtain an overall pattern
Make sure that traffic hits the relevant queues
Produce a secondary template to generate irrelevant traffic
Generate irrelevant traffic and obtain an overall pattern
Make sure that traffic now hits the default queue (if need be)

Parameters:

flow_rule_rss	A flow rule featuring RSS action
isolated	Isolated mode toggle
promiscuous	Promiscuous mode toggle