Skip test when hardware sample rates mismatch in data path test

[q23175401]

This adds a check to skip tests where the input and output hardware sample rates don't match when using a USB device (direct loopback), to avoid test failures caused by the mismatch.

[robertwu1]

LGTM! Thanks for doing this!

[flamme]

This doesn't really make sense to me. The hardware sample rate API returns the configuration of the particular input or output stream configuration in the HAL side. This doesn't mean the USB device is opened in different configuration. The DSP can always open the device at a different configuration and do conversion. Why it is needed to skip the test?

[robertwu1]

The issue is that if the DSP has one hardware input sample rate and a different output sample rate, it can be very hard for it to do conversions efficiently. This is just like on the app side where we are opening the stream at the same input sample rate and output sample rate. Obviously this should work in all cases but in reality it's hard for some of these cases for this to work correctly, especially with something like a peripheral attached.