Enable IWD to be used as back-end in network selection

[h8d13]

This PR should solve a lot of issues for Intel users among other legacy hardware.

Issue originally from user: Coda_Phi : On a surface pro 7 (Notoriously Intel contributes to IWD dev, and has bad support with default wpa_supplicant default backend) This notably results in "No networks" in desktops.

So I tested a little on a Intel AX211 similar to user's AX201

It follows https://wiki.archlinux.org/title/NetworkManager#Using_iwd_as_the_Wi-Fi_backend
And https://wiki.archlinux.org/title/NetworkManager#iwd_support_for_captive_portal_support_on_legacy_hardware

By setting enable services to False then enabling only NetworkManager and writing the necessary config file to use IWD as back-end. It also still copies from ISO re-using existing definitions too.

Simply makes it so that you configure in ISO env before or during archinstall => Still works in DE

[svartkanin]

The wpa_supplication package is installed by default

archinstall/archinstall/default_profiles/desktop.py

Line 35 in 601e033

'wpa_supplicant',

, I think this will need to be only added if the default NM is selected.

[h8d13]

Maybe we hold on to this for a little testing on appropriate hardware

[Torxed]

I think this looks good to go in now.
Future idea: maybe by selecting NM we can have a sub-menu or something to "configure" it, when it's selected a submenu could be to "select backend".. or just a "popup" asking :)

But that can be a separate/later PR when the new TUI is in.

[svartkanin]

I think the "Copy ISO config" option is somewhat misleading altogether as it won't copy any manually setup wifi networking which would be ideal as I imagine laptop users will mostly connect to it