samples: tests: Improve accuracy of required dependencies in networking tests

[katgiadla]

Problem description:
Majority of the networking testcases require any network interface - this requirement is specified in testsuite YAML by using keyword netif.
On the boards, which support this feature, it is possible to build and/or execute test configuration.

Some test suites assume that specific networking technology will be used (example for Ethernet and for OpenThread).

Unfortunatelly, these technologies are not accurate specified. It means, samples/tests are build and/or execute on the boards, which does not support specified technology but support any network interface.

Solution:
Clarify, which network feature is required in testsuites/sample by changing field depends_on.
e.g. example for Ethernet

Currently:
depends_on: netif

Change into:
depends_on: eth

[zephyrbot]

Hi @rlubos,

This issue, marked as an Enhancement, was opened a while ago and did not get any traction. Please confirm the issue is correctly assigned and re-assign it otherwise.

Please take a moment to review if the issue is still relevant to the project. If it is, please provide feedback and direction on how to move forward. If it is not, has already been addressed, is a duplicate, or is no longer relevant, please close it with a short comment explaining the reason.

@katgiadla you are also encouraged to help moving this issue forward by providing additional information and confirming this request/issue is still relevant to you.

Thanks!

[rlubos]

For samples. I've opened #69295 to narrow the testing scope for the specialized ones (mostly Ethernet stuff, the only OT speicifc is the linked one).

As for the tests, I've looked them over but I'm not really sure we should change anything there. All of the tests we have (unless I missed something) do not really depend on the actual hardware, as they operate on fake interfaces they create.

[jukkar]

Also after #69244 the tests should run without any board specific Ethernet interfaces.