dns priority with wired and cellular modem connection enabled

[Stefal]

Describe the bug
With wired and cellular modem connection enabled, the first dns server used seems to be the one from the cellular modem, even though it's metric value is higher than the wired one.

To Reproduce
Steps to reproduce the behavior:

1. nmcli shows :

DNS configuration:
        servers: 192.168.0.1
        interface: enxae0c29a39b6d
        
        servers: 192.168.1.253
        domains: lan
        interface: end0

inside the nmcli connection, dns priority are both set to 0

$ nmcli connection show 'Cellular Modem' | grep dns
connection.mdns:                        -1 (default)
connection.dns-over-tls:                -1 (default)
ipv4.dns:                               --
ipv4.dns-search:                        --
ipv4.dns-options:                       --
ipv4.dns-priority:                      0
ipv4.ignore-auto-dns:                   no
ipv6.dns:                               --
ipv6.dns-search:                        --
ipv6.dns-options:                       --
ipv6.dns-priority:                      0
ipv6.ignore-auto-dns:                   no

$ nmcli connection show 'Wired connection 1' | grep dns
connection.mdns:                        -1 (default)
connection.dns-over-tls:                -1 (default)
ipv4.dns:                               --
ipv4.dns-search:                        --
ipv4.dns-options:                       --
ipv4.dns-priority:                      0
ipv4.ignore-auto-dns:                   no
ipv6.dns:                               --
ipv6.dns-search:                        --
ipv6.dns-options:                       --
ipv6.dns-priority:                      0
ipv6.ignore-auto-dns:                   no
3. Click on '....'
4. Scroll down to '....'
5. See error

$ ip route
default via 192.168.1.253 dev end0 proto dhcp src 192.168.1.127 metric 101
default via 192.168.0.1 dev enxae0c29a39b6d proto dhcp src 192.168.0.100 metric 900
192.168.0.0/24 dev enxae0c29a39b6d proto kernel scope link src 192.168.0.100 metric 900
192.168.1.0/24 dev end0 proto kernel scope link src 192.168.1.127 metric 101
192.168.3.0/24 dev enx1a3202991545 proto kernel scope link src 192.168.3.214 metric 100

Expected behavior
The dns server on the connection with the lowest metric value should have the priority