An automated way to use a Static IP with Tang disk on VMware UPI

1. Proposed title of this feature request
An automated way to use a Static IP with Tang disk on VMware install. 

2. What is the nature and description of the request?
An automated way to use a Static IP with Tang disk on VMware install. 

Currently, the only way to do this is with a separate ignition config file on each node.

Example:

1. cat worker0-static-ip-tang.rcc
   variant: rhcos
   version: 0.1.0
   ignition:
     config:
       merge:
         - local: worker.ign
   systemd:
     units:
       - name: static-ip-karg.service
         enabled: true
         contents: |
             [Unit]
             Description=Append karg via oneshot
             ConditionPathExists=/run/ostree-booted
             ConditionFirstBoot=yes
             Before=machine-config-daemon-firstboot.service
             After=boot-complete.target
             [Service]
             ExecStart=/usr/bin/rpm-ostree kargs --append="ip=192.168.xxx.xx::192.168.xxx.1:255.255.255.0:worker0.cluster2.openshift.lan:enp1s0:none nameserver=192.168.xxx.1"
             Type=oneshot
             RemainAfterExit=yes
    
             [Install]
             WantedBy=multi-user.target

3. Why does the customer need this? (List the business requirements here)
Having to make a separate ignition file for each node is a hindrance and slows the customer down from automating this process. 

4. List any affected packages or components.
openshift-install