About the command ‘nmcli connection migrate’, could it support changing the connection id and the keyfile name when migrate?

Background
Failed to leapp upgrade from rhel-9.6 to rhel-10.0 with the legacy network configuration
The default network renderer is sysconfig when deploy rhel-9.6 with cloud-init default config, but it doesn't support sysconfig configuration files in legacy "ifcfg" format in rhel-10.0, so there is inhibitor error when leapp upgrade from rhel-9.6 to rhel-10.0 with the legacy network configuration files(ifcfg-xxx) , which caused the leapp upgrade process to fail.

Now we have to run below commands as a workaround,

nmcli connection modify 'System eth0' connection.id 'cloud-init eth0' 
nmcli connection migrate /etc/sysconfig/network-scripts/ifcfg-eth0 
sudo mv /etc/NetworkManager/system-connections/'cloud-init eth0.nmconnection' /etc/NetworkManager/system-connections/cloud-init-eth0.nmconnection 
nmcli conn reload

Why choose 'cloud-init eth0' as the connection id and 'cloud-init-eth0' as the file name? because of cloud-init, for rhel 10 it uses NM as network render and it defines the name like that ("id": f"cloud-init {con_id}",  and  con_file = f"cloud-init-{con_id}.nmconnection").   https://github.com/canonical/cloud-init/blob/main/cloudinit/net/network_manager.py
 
It would be better to make the steps much easier for users/customers to follow and apply.