The user-v2 leases.json file will not be automatically created and will not take effect.

### Description

I found a very confusing phenomenon. When the virtual machine is set to plain to true, the function of creating leases.json in user-v2 will be invalid. At the same time, it is impossible to statically control the fixed IP through this file. Is this due to Lima's design logic or an abnormal phenomenon?
## device info
macbook pro m4pro
cpu arch: aarch64

## network.yaml
paths:
socketVMNet: "/opt/socket_vmnet/bin/socket_vmnet"
varRun: /private/var/run/lima
sudoers: /private/etc/sudoers.d/lima

group: everyone

networks:
shared:
mode: shared
gateway: 192.168.105.1
dhcpEnd: 192.168.105.254
netmask: 255.255.255.0
bridged:
mode: bridged
interface: en0
# bridged mode doesn't have a gateway; dhcp is managed by outside network
host:
mode: host
gateway: 192.168.106.1
dhcpEnd: 192.168.106.254
netmask: 255.255.255.0
k8s:
mode: user-v2
gateway: 10.1.1.1
netmask: 255.255.255.0
interface: ""

### vm yaml
arch: aarch64
plain: true
cpus: 4
memory: "6GiB"
disk: "28GiB"
vmType: "vz"
images:
- location: https://dl.rockylinux.org/pub/rocky/9/images/aarch64/Rocky-9-GenericCloud.latest.aarch64.qcow2
arch: aarch64
networks:
- lima: k8s
- vzNAT: true
containerd:
system: false
user: false