#10517: feat: Add Bonjour interface binding config option

# Add Bonjour interface binding configuration ### Problem On multi-homed systems where multiple network interfaces are active on the same subnet (e.g., Ethernet and Wi-Fi both connected to the same LAN), OpenClaw's Bonjour/mDNS service advertiser registers on all interfaces simultaneously. This causes continuous name conflicts as each interface attempts to claim the same service name, resulting in repeated warnings in logs: ``` gateway name conflict resolved; newName="<hostname> (OpenClaw) (N)" ``` The counter increments indefinitely as the conflict resolver keeps renaming the service. ### Solution This PR adds a new configuration option gateway.bonjour.interface that allows binding Bonjour/mDNS advertising to specific network interface(s). The underlying @homebridge/ciao library already supports interface binding through its MDNSServerOptions.interface parameter. ### Configuration The new option accepts either a single interface name or an array of interface names: ```json { "gateway": { "bonjour": { "interface": "en0" } } } ``` or ```json { "gateway": { "bonjour": { "interface": ["en0", "en1"] } } } ``` Interface names can be specified as: - Interface names: "en0", "en1", etc. - IP addresses: "192.168.1.100" ### Changes...