Description of problem:
One of my customer manually converted the existing NIC templates and added `<role>NetworkConfigTemplate` to
the `parameter_defaults` in the network-environment.yaml before executing the `openstack undercloud upgrade`.

They also removed the `OS::TripleO::<role>::Net::SoftwareConfig` parameter from the `resource_registry` as noted
in our documentation.

After running the `openstack undercloud upgrade`, the tripleo-overcloud-baremetal-deployment.yaml file was created
in /home/stack/overcloud-deploy/overcloud/ as expected, but there was a WARNING message saying "No network config
found for role ...", and the `network_config` `template` was `null`. Additionally, there were no NIC templates in
/home/stack/overcloud-deploy/overcloud/nic-configs/, and /home/stack/overcloud-deploy/overcloud/overcloud-network-
environment.yaml was also missing.

tripleo-overcloud-baremetal-deployment.yaml
~~~

1. Generated with the following on 2024-XX-XXTXX:XX:XX.428158
   #
2. openstack overcloud node extract provisioned --stack overcloud --roles-file /tmp/tmpbtbcpcd1 --output /home/stack/overcloud-deploy/overcloud/tripleo-overcloud-baremetal-deployment.yaml --working-dir /home/stack/overcloud-deploy/overcloud --yes
   #

1. WARNING: No network config found for role Controller. Please edit the file and set the path to the correct network config template. <====
2. WARNING: No network config found for role ComputeOvsDpdk. Please edit the file and set the path to the correct network config template. <====
   #

• name: Controller
  count: 3
  hostname_format: '%stackname%controller%index%'
  defaults:
  network_config:
  default_route_network:
• External
  network_config_update: false
  physical_bridge_name: br-ex
  public_interface_name: nic1
  template: null <==================
  ...
  ~~~

Version-Release number of selected component (if applicable):
Red Hat OpenStack Platform release 17.1.3
python3-tripleoclient.noarch 16.5.1-17.1.20230927003758.el8ost

How reproducible:
Reproducibility has not been confirmed. The issue occurs only in the customer's environment.
The customer has already manually created the NIC template and completed the FFU successfully.

Actual results:
There are no NIC templates in /home/stack/overcloud-deploy/overcloud/nic-configs/ after undercloud upgrade.
/home/stack/overcloud-deploy/overcloud/overcloud-network-environment.yaml is missing after undercloud upgrade.

Expected results:
NIC template and overcloud-network-environment.yaml are created after undercloud upgrade.