MAAS 3.5.2 does not fully configure network device when doing so in UI

Describe the bug:
I reported this against 2.7, and it was fixed then:
https://bugs.launchpad.net/maas/+bug/1878932

and seems to have regressed. I was configuring devices on a server (donkeykong) on Main MAAS in TOR-3 this morning and ran into this issue on EVERY network device. As before, I've added a video showing the issue. My apologies that the video doesn't show the drop-downs, but you can see where I set each configuration option, save the config, only to have MAAS ignore the subnet and IP address setting, forcing me to go in a second time and re-reconfigure the device in order to complete the configuration.

Steps to reproduce:
* Pick a machine with devices that are not configured and have an unusual fabric
* Pick an unconfigured network device
* Choose the Edit Physical option for the device
  * change to correct fabric
  * set the correct VLAN
  * Choose the correct subnet
  * set the device to DHCP
* Click Save
* Review the network tab information and now note the fabric changed but the subnet and IP address settings were discarded.
* Go back into Edit Physical for the device, set the subnet and IP AGAIN, and save again, and NOW the device is fully configured.

Expected behavior (what should have happened?):

All config options set are saved and then displayed on the network tab without having to set config options twice for each network device.

Actual behavior (what actually happened?):

As the video shows, I have to set the network config twice for each port configured.

MAAS version and installation type (deb, snap):

3.5.2, and no idea on installation type, the MAAS team owns the installation and has deployed it.

MAAS setup (HA, single node, multiple regions/racks):

HA

Host OS distro and version:

Ubuntu... 24.04? Not sure what was used on the VMs on the Edge Cloud stack, I didn't have any part in that deployment.

Additional context:

See attached video for a demonstration of the bug.