Discovery Service Affiliate Audit Controller

[Artem Chernyshev]

Would rather not put that to the machine set status controller.
Need to clean up the destroyed machines members from the discovery service.

Otherwise things like cluster recreation from etcd backups fails due to the conflicting ip addresses.

Ilustration of the problematic kubespan peer statuses:

192.168.88.81   kubespan    KubeSpanPeerStatus   2CDZosuUNmNzoap0oi7AjuzHTIQ8T9Aze9w/KHxatCw=   4         cp-1                192.168.89.129:51820   unknown   0       1480
192.168.88.81   kubespan    KubeSpanPeerStatus   6BSE6Jtx/HQM8SJLrt51Bf8n25NZV/Y6I7QYXnlcXRU=   6         ruch-vbox-storage   77.108.97.220:51820    up        20060   12948
192.168.88.81   kubespan    KubeSpanPeerStatus   FxDwBDQphUHdYWRH59RcHiw7EsqEGx1p4oolHzeCcxI=   3         rockpi4-storage     192.168.88.10:51820    up        19676   12500
192.168.88.81   kubespan    KubeSpanPeerStatus   L6bqRdXqh70HGdy8I2XkhnU69mtIMBo/P2x/eEKLvQ4=   4         cp-0                77.108.97.212:1099     unknown   0       1480
192.168.88.81   kubespan    KubeSpanPeerStatus   WzDJ23MuoE8JBH48T95PZIL5lcwNwyfgVVxLHlBW4Gg=   3         proxmox-storage     192.168.89.131:51820   up        124     212
192.168.88.81   kubespan    KubeSpanPeerStatus   d8LQYcAIOs32ir7Rmq2vyp5/O8PqT9OVOaT6M5CMKXs=   4         rpi4-8gb            77.108.97.212:1096     unknown   0       1480
192.168.88.81   kubespan    KubeSpanPeerStatus   fzhSZATNLcXKETCe7QvjHlUvZ51FK1upiYk8qPcFHQg=   4         rpi4-8gb            77.108.97.212:1096     unknown   0       1480
192.168.88.81   kubespan    KubeSpanPeerStatus   gxsuUsUd06cq0JTL8zcDLWdrX7P+rbfY+7wscp7WQwg=   4         cp-1                77.108.97.212:1098     unknown   0       1480
192.168.88.81   kubespan    KubeSpanPeerStatus   hBm6yyEdeIyRqoKJawo9lq6ncCV41AoNv2mt2eFHw38=   4         cp-0                77.108.97.212:1099     unknown   0       1480