[Feature Request] Ensure use of NetworkManager Key-files instead of ifcfg files

Is your feature request related to a problem? Please describe.

As noted in AMIgen9 #22:

While writing security-automation for the watchmaker project (see: ash-linux-formula https://github.com/plus3it/ash-linux-formula/pull/506), a security-finding came up for the network configuration files. This led me to find a vendor-article on the deprecation of ifcfg files in RHEL 9 and later (see the "NetworkManager connection profiles in ifcfg format are deprecated" section of the linked-document for specific verbiage). The AMIgen automation needs to be updated to account for this change

There are similar notes for RHEL8 noting that the deprecation is pending: it might be a good idea to update the EL8 automation to better align to that pending-deprecation and associated warning.

Describe the solution you'd like

As with the previously-linked AMIgen9 issue:

AMIgen bakes in the cloud-init service. Instances launched from AMIgen-created images already leverage cloud-init for boot-time automation-tasks. The ifcfg to NM-keyfile operation could be included by way of a per once stage script.

Describe alternatives you've considered

Additional context

Start by locating the cloud-init configuration and per-once stage used by AMIgen, then review how EL8 network configuration is generated. Done means the image automation accounts for NetworkManager key-files instead of ifcfg files and addresses the noted pending deprecation for EL8.