feat(config): wildcard interface name support & refactor lazybind

[LostAttractor]

Background

#724
该PR抽象了lazybind的能力以便后续其他功能使用（主要是后续在routing中过滤interface需要）
该PR实现的功能与 #729 类似
此外，为wan也加入了lazybind

Checklist

• The Pull Request has been fully tested
• There's an entry in the CHANGELOGS
• There is a user-facing docs PR against https://github.com/daeuniverse/dae

Full Changelogs

• interface name now support wildcard
• wan interface now support lazybind

Issue Reference

Closes #724
Closes #729

Test Result

[mzz2017]

#724是个issue，不是pr

[mzz2017]

Closes #724
Closes #729

[github-xihe]

我ImmortalWrt 24.10.0同时使用dae和NATMap，测试重启pppoe接口后，会导致NATMap失效和dae外网域名解析失败上不了，TG纯IP能连，只有service dae restart才会两个恢复正常。


dae这边就只会刷检测节点，service dae restart后会恢复正常，NATMap也能解析

[LostAttractor]

NATMap

你重启pppoe后ip一般都会变，NATMap当然会掉
至于dae的问题，请问tcpdump -ni dae0是否有流量，tc filter show dev pppoe-wan ingress是否有dae_wan_ingress条目

[github-xihe]

NATMap

你重启pppoe后ip一般都会变，NATMap当然会掉 至于dae的问题，请问tcpdump -ni dae0是否有流量，tc filter show dev pppoe-wan ingress是否有dae_wan_ingress条目

我知道重启pppoe后ip会变，但不运行service dae restart就一直解析不了。后面我把NATMap的通知脚本延迟10S以上，测试了重启几次pppoe也没出现上面两种情况了，更多测试等后面6-7天ip自动更新pppoe重拨再看看。

[dae-prow]

🧪 Since the PR has been fully tested, please consider merging it.

[mzz2017]

LGTM.

[mzz2017]

Awesome! Thank you!