Description of problem:

Satellite doesn't support keyfiles when provisioning RHEL9: it creates ifcfg during provisioning.

RHEL9 installed from Satellite are thus creating duplicated and confusing files

tl;dr: *It seems Anaconda creates the keyfiles/snippets used by RHEL9 and at the same time Kickstart from Satellite is creating ifcfg files duplicating the configuration!*

Example of a Physical Machine with bond:
~~~
[root@rkauslsp004 ~]# ls -ll /etc/NetworkManager/system-connections
total 12
rw------. 1 root root 425 Oct 10 12:18 bond0.nmconnection
rw------. 1 root root 282 Oct 10 12:18 ens3f0.nmconnection
rw------. 1 root root 282 Oct 10 12:18 ens3f1.nmconnection
[root@rkauslsp004 ~]# ls -ll /etc/sysconfig/network-scripts/
total 12
rw-rr-. 1 root root 309 Oct 10 12:19 ifcfg-bond0
rw-rr-. 1 root root 129 Oct 10 12:19 ifcfg-ens3f0
rw-rr-. 1 root root 129 Oct 10 12:19 ifcfg-ens3f1
~~~

Example simple Virtual Machine (Vmware):
~~~
[root@haaslvupgrade ~]# ls -ll /etc/NetworkManager/system-connections
total 4
rw------. 1 root root 417 Oct 10 12:54 ens192.nmconnection
[root@haaslvupgrade ~]# ls -ll /etc/sysconfig/network-scripts/
total 4
rw-rr-. 1 root root 252 Oct 10 12:55 ifcfg-ens192
~~~

This makes managing systems very confusing for customers as keyfiles by default will be prioritized.

Satellite should support keyfiles when installing RHEL9 or only use ifcfg files (if supported by anaconda)

What is the business impact? Please also provide timeframe information.
High

Where are you experiencing the behavior? What environment?
Production

When does the behavior occur? Frequency? Repeatedly? At certain times?
Always

Version-Release number of selected component (if applicable):
Satellite 6.11.3 deploying RHEL 9.0

How reproducible:
Always

Expected results:
Due to the nature and how customers use the installations, they actually need to remove the keyfiles created by Anaconda and only use the ifcfg-rh for the time being.

Since it's required to be able to manage the network via Satellite, currently using keyfiles is not ideal!

What we would expect is that Satellite fully supports keyfiles or at least support both installation methods (ifcfg-xxx *and* keyfiles)