netdev_default: migrate to netif_dev_default

[jia200x]

Contribution description

This PR renames netdev_default to netif_dev_default due to the following reasons:

1. With the on-going migration to non-netdev devices (e.g Radio HAL), netdev_default is misleading.
2. From an IoT OS perspective, IMO it makes sense to bring "default network interfaces" instead of network devices, as the network devices are not necessarily complete (e.g a MAC layer may be missing).

At the same time, this PR allows to define granularity for the kind of network interfaces (e.g select only IEEE 802.15.4 devices/interfaces). This is specially useful for test applications such as ieee802154_hal, which still require any IEEE 802.15.4 device but does not require other embedded network devices (e.g WiFi, Ethernet).

So far, this PR only defines the MODULE_NETIF_DEV_IEEE802154_DEFAULT granularity, but we should add more on demand.

Testing procedure

Compile tests should be enough. Make sure TEST_KCONFIG=1 and TEST_KCONFIG=0 builds converge.

Issues/PRs references

It will simplify merging #18472.

[jia200x]

no idea why it was marked as a draft. This is ready for review

[riot-ci]

Murdock results

❌ FAILED

3bdab84 fixup! netdev_default: migrate to netif_dev_default

Success	Failures	Total	Runtime
1526	0	6882	03m:05s

Artifacts

[benpicco]

This should probably remain gnrc_netdev_default

[jia200x]

uh, that's a result of sed. I will revert it.

[benpicco]

Is there no fallback to include netif_dev_default if netdev_default is selected by an external application?

Do I understand it correctly that netif_dev_default would now select netif_dev_ieee802154_default, so that applications that don't care about the type of network interface will get whatever the board provides, while 6lo specific apps would select netif_dev_ieee802154_default?

(Although those would also work on esp_now, nrfmin, cc110x or nrf24l01p_ng - so should we have another netif_dev_6lo_default that then can select netif_dev_ieee802154_default?

[jia200x]

Is there no fallback to include netif_dev_default if netdev_default is selected by an external application?

Yes, it was there, but it got replaced by sed. I will fix that immediately.

Do I understand it correctly that netif_dev_default would now select netif_dev_ieee802154_default, so that applications that don't care about the type of network interface will get whatever the board provides, while 6lo specific apps would select netif_dev_ieee802154_default?

Exactly.

(Although those would also work on esp_now, nrfmin, cc110x or nrf24l01p_ng - so should we have another netif_dev_6lo_default that then can select netif_dev_ieee802154_default?

That would make sense. But since there are too many link layers, I just wanted to start with the baseline + IEEE 802.15.4. We could then migrate apps and tests as needed.

[jia200x]

done!

[jia200x]

ping. It seems this will be required for #19015

[benpicco]

Kconfig is not happy still

[benpicco]

This needs a rebase and Kconfig needs to be fixed.
What do you think of introducing netif_dev_6lo_default? I'm thinking of the border router in particular where we support more than just IEEE 802.15.4 for the 6lo part.

[jia200x]

What do you think of introducing netif_dev_6lo_default? I'm thinking of the border router in particular where we support more than just IEEE 802.15.4 for the 6lo part.

Good idea. I can add that while rebase