plugins: Wireguard does not start when using dns name instead ip

This is a special condition, when using following configuration:

1. Unbound
2. Bind
3. WireGuard

If you run your domain via your BIND on the same OpnSense as Wireguard and use a name from that domain for your endpoint, the service start for wireguard will fail (mostly) on reboot.

The rc.d order of starting services says for named:

# PROVIDE: named
# REQUIRE: NETWORKING ldconfig syslogd
# BEFORE: SERVERS

and for unbound:

# PROVIDE: unbound
# REQUIRE: FILESYSTEMS defaultroute netwait resolv
# BEFORE: NETWORKING

and for wireguard / openvpn:

# PROVIDE: wireguard
# REQUIRE: NETWORKING

Here the wireguard service may try to start BEFORE named is running.

If it would be for named (changed BEFORE list):

# PROVIDE: named
# REQUIRE: NETWORKING ldconfig syslogd
# BEFORE: SERVERS wireguard

all will run fine.

Is this suitable for a PR or change or how to you think about it?

Cheers Tom