bookworm versus noble - i40e netdevice name discrepancy

[Robert Moulton]

When an Ubuntu 24.04 (noble) system with an i40e network adapter is
built with the Debian bookworm nfsroot image, 'eno1' is set as the
network device name and subsequently used for the netplan
configuration file:

# grep -ir eno1 /var/log/fai/gac-p233/last
/var/log/fai/gac-p233/last/fai.log:eno1             UP
3c:ec:ef:fb:6d:a8 <BROADCAST,MULTICAST,UP,LOWER_UP>
/var/log/fai/gac-p233/last/fai.log:eno1             UP
10.66.59.33/21 fe80::3eec:efff:fefb:6da8/64
/var/log/fai/gac-p233/last/fai.log:eno1 rx_bytes 1708.46 Mbytes
/var/log/fai/gac-p233/last/fai.log:eno1 tx_bytes 14.97 Mbytes
/var/log/fai/gac-p233/last/variables.log:NIC1=eno1
/var/log/fai/gac-p233/last/variables.log:netdevices='eno1 '
/var/log/fai/gac-p233/last/variables.log:netdevices_all='eno1 eno2
enxbe3af2b6059f '
/var/log/fai/gac-p233/last/variables.log:netdevices_up='eno1 '
/var/log/fai/gac-p233/last/scripts.log:Generating netplan
configuration for eno1 (dhcp)
/var/log/fai/gac-p233/last/dmesg.log:[    4.064088] i40e 0000:65:00.0
eno1: renamed from eth0
/var/log/fai/gac-p233/last/dmesg.log:[    5.327400] IPv6:
ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
/var/log/fai/gac-p233/last/boot.log:netdevices_all="eno1 eno2 enxbe3af2b6059f "
/var/log/fai/gac-p233/last/boot.log:netdevices_up="eno1 "
/var/log/fai/gac-p233/last/boot.log:netdevices="eno1 "
/var/log/fai/gac-p233/last/boot.log:NIC1=eno1

But upon booting the newly-built Ubuntu system, the network device
name is discovered/set as 'eno1np0':

# dmesg | grep -i eth
[    4.718549] i40e: Intel(R) Ethernet Connection XL710 Network Driver
[    4.985699] i40e 0000:65:00.0 eth0: NIC Link is Up, 1000 Mbps Full
Duplex, Flow Control: None
[    5.256134] i40e 0000:65:00.1 eth1: NIC Link is Up, 1000 Mbps Full
Duplex, Flow Control: None
[    5.303170] i40e 0000:65:00.0 eno1np0: renamed from eth0
[    5.319797] i40e 0000:65:00.1 eno2np1: renamed from eth1
[    5.595012] usb 1-7.2: Product: RNDIS/Ethernet Gadget
[    5.616735] usbcore: registered new interface driver cdc_ether

Naturally the interface doesn't get activated as a result.

How might this issue be addressed?