uc18 console-conf conflicts with cloud-init nocloud data source

[Ian Johnson]

If I use the following cloud-init user-data and meta-data with the nocloud data source:

user-data file:

#cloud-config
password: some-kind-of-password
chpasswd: { expire: False }
ssh_pwauth: True

meta-data file:

instance-id: iid-local01
local-hostname: cloudimg

on my first boot of a uc18 image on a raspi4, then when snapd finishes seeding and hits console-conf, console-conf cannot continue to the "identity" page where I supply my email address because it complains thusly:

                         Network configuration failed:
            "/etc/netplan/00-snapd-config.yaml:5:7: Error in network
        definition: eth0: 'set-name:' requires 'match:' properties\n
                            addresses: []\n ^\n"

The full traceback from /var/log/console-conf/subiquity-debug.log is here: https://pastebin.ubuntu.com/p/vbrkkCfj6B/

My expectation as a user is that since my cloud-init is quite simple, it would not interfere with any network related settings such that I could also use console-conf independently of my cloud-init.