Homebridge listening on all network interfaces despite bridge.bind config
### Analysis

My config looks like this:
```
{
    "bridge": {
       ...
        "bind": [
            "ens19"
        ]
    },
    ...
}
```
because I want Homebridge to only listen on `ens19` interface.

But, looking at the logs it seems that Homebridge binds all network interfaces despite this config:

```
...
homebridge-homebridge-1  | Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
homebridge-homebridge-1  | New relevant interface docker0.IPv4 for mDNS.
homebridge-homebridge-1  | Joining mDNS multicast group on interface ens20.IPv4 with address 192.168.1.4.
homebridge-homebridge-1  | New relevant interface ens20.IPv4 for mDNS.
homebridge-homebridge-1  | Joining mDNS multicast group on interface ens19.IPv4 with address 192.168.1.3.
homebridge-homebridge-1  | New relevant interface ens19.IPv4 for mDNS.
homebridge-homebridge-1  | Joining mDNS multicast group on interface ens18.IPv4 with address 192.168.1.2.
homebridge-homebridge-1  | New relevant interface ens18.IPv4 for mDNS.
homebridge-homebridge-1  | Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
homebridge-homebridge-1  | New relevant interface lo.IPv4 for mDNS.
homebridge-homebridge-1  | Network interface enumeration completed.
homebridge-homebridge-1  | Registering new address record for 172.17.0.1 on docker0.IPv4.
homebridge-homebridge-1  | Registering new address record for fe80::5843:93ff:fe31:b6d on ens20.*.
homebridge-homebridge-1  | Registering new address record for 192.168.1.4 on ens20.IPv4.
homebridge-homebridge-1  | Registering new address record for fe80::102f:5fff:feb9:8756 on ens19.*.
homebridge-homebridge-1  | Registering new address record for 192.168.1.3 on ens19.IPv4.
homebridge-homebridge-1  | Registering new address record for fe80::189e:edff:fef4:7a15 on ens18.*.
homebridge-homebridge-1  | Registering new address record for 192.168.1.2 on ens18.IPv4.
homebridge-homebridge-1  | Registering new address record for ::1 on lo.*.
homebridge-homebridge-1  | Registering new address record for 127.0.0.1 on lo.IPv4.
...
```

We can also see it with `sudo lsof -i -P -n | grep LISTEN`:
```
hb-servic 1601     root   20u  IPv6  19695      0t0  TCP *:8581 (LISTEN)
homebridg 1631     root   19u  IPv6  19710      0t0  TCP *:51197 (LISTEN)
```

### Expected Behavior

I expect that Homebridge binds its services only on the interface given in `bridge.bind` array.

### Steps To Reproduce

1. Create at least two network interfaces on your virtual machine
2. Select only one network interface in `bridge.bind` array of `config.json`
3. Restart Homebridge and check the logs, you will see that all interfaces of your host are used by Homebridge.

### Logs

```markdown
homebridge-homebridge-1  | s6-rc: info: service homebridge-log successfully started
homebridge-homebridge-1  | s6-rc: info: service legacy-services: starting
homebridge-homebridge-1  | s6-rc: info: service legacy-services successfully started
homebridge-homebridge-1  | [7/26/2023, 9:59:36 AM] [HB Supervisor] Homebridge Storage Path: /var/lib/homebridge
homebridge-homebridge-1  | [7/26/2023, 9:59:36 AM] [HB Supervisor] Homebridge Config Path: /var/lib/homebridge/config.json
homebridge-homebridge-1  | [7/26/2023, 9:59:36 AM] [HB Supervisor] Logging to /var/lib/homebridge/homebridge.log
homebridge-homebridge-1  | [7/26/2023, 9:59:36 AM] [HB Supervisor] OS: Linux 6.1.0-10-amd64 x64
homebridge-homebridge-1  | [7/26/2023, 9:59:36 AM] [HB Supervisor] Node.js v18.16.0 /opt/homebridge/bin/node
homebridge-homebridge-1  | [7/26/2023, 9:59:36 AM] [HB Supervisor] Homebridge Path: /var/lib/homebridge/node_modules/homebridge/bin/homebridge
homebridge-homebridge-1  | [7/26/2023, 9:59:36 AM] [HB Supervisor] UI Path: /opt/homebridge/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
homebridge-homebridge-1  | Starting Avahi daemon
homebridge-homebridge-1  | Found user 'avahi' (UID 105) and group 'avahi' (GID 108).
homebridge-homebridge-1  | Successfully dropped root privileges.
homebridge-homebridge-1  | avahi-daemon 0.8 starting up.
homebridge-homebridge-1  | No service file found in /etc/avahi/services.
homebridge-homebridge-1  | Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
homebridge-homebridge-1  | New relevant interface docker0.IPv4 for mDNS.
homebridge-homebridge-1  | Joining mDNS multicast group on interface ens20.IPv4 with address 192.168.1.4.
homebridge-homebridge-1  | New relevant interface ens20.IPv4 for mDNS.
homebridge-homebridge-1  | Joining mDNS multicast group on interface ens19.IPv4 with address 192.168.1.3.
homebridge-homebridge-1  | New relevant interface ens19.IPv4 for mDNS.
homebridge-homebridge-1  | Joining mDNS multicast group on interface ens18.IPv4 with address 192.168.1.2.
homebridge-homebridge-1  | New relevant interface ens18.IPv4 for mDNS.
homebridge-homebridge-1  | Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
homebridge-homebridge-1  | New relevant interface lo.IPv4 for mDNS.
homebridge-homebridge-1  | Network interface enumeration completed.
homebridge-homebridge-1  | Registering new address record for 172.17.0.1 on docker0.IPv4.
homebridge-homebridge-1  | Registering new address record for fe80::5843:93ff:fe31:b6d on ens20.*.
homebridge-homebridge-1  | Registering new address record for 192.168.1.4 on ens20.IPv4.
homebridge-homebridge-1  | Registering new address record for fe80::102f:5fff:feb9:8756 on ens19.*.
homebridge-homebridge-1  | Registering new address record for 192.168.1.3 on ens19.IPv4.
homebridge-homebridge-1  | Registering new address record for fe80::189e:edff:fef4:7a15 on ens18.*.
homebridge-homebridge-1  | Registering new address record for 192.168.1.2 on ens18.IPv4.
homebridge-homebridge-1  | Registering new address record for ::1 on lo.*.
homebridge-homebridge-1  | Registering new address record for 127.0.0.1 on lo.IPv4.
homebridge-homebridge-1  | [7/26/2023, 9:59:37 AM] [Homebridge UI] Homebridge Config UI X v4.50.4 is listening on :: port 8581
homebridge-homebridge-1  | Server startup complete. Host name is localserver.local. Local service cookie is 3937533006.
homebridge-homebridge-1  | [7/26/2023, 9:59:37 AM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution
homebridge-homebridge-1  | [7/26/2023, 9:59:37 AM] [HB Supervisor] Started Homebridge v1.6.1 with PID: 142
homebridge-homebridge-1  | [7/26/2023, 9:59:38 AM] Loaded config.json with 0 accessories and 1 platforms.
homebridge-homebridge-1  | [7/26/2023, 9:59:38 AM] Loaded 0 cached accessories from cachedAccessories.
homebridge-homebridge-1  | [7/26/2023, 9:59:38 AM] ---
homebridge-homebridge-1  | [7/26/2023, 9:59:38 AM] No plugins found.
homebridge-homebridge-1  | [7/26/2023, 9:59:38 AM] Loading 1 platforms...
homebridge-homebridge-1  | Setup Payload:
homebridge-homebridge-1  | X-HM://002443TYRJ2B8
homebridge-homebridge-1  | Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
homebridge-homebridge-1  |
homebridge-homebridge-1  |     ┌────────────┐
homebridge-homebridge-1  |     │ XXXXXXXXX  │
homebridge-homebridge-1  |     └────────────┘
homebridge-homebridge-1  |
homebridge-homebridge-1  | [7/26/2023, 9:59:38 AM] Homebridge v1.6.1 (HAP v0.11.1) (Homebridge FF17) is running on port 51197.
```


### Configuration

```json
{
    "bridge": {
        "name": "Homebridge FF17",
        "username": "0E:43:E0:13:FF:17",
        "port": 51197,
        "pin": "389-23-891",
        "advertiser": "bonjour-hap",
        "bind": [
            "ens19"
        ]
    },
    "accessories": [],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        }
    ]
}
```


### Environment

- OS: Debian 12
- Homebridge v1.6.1 (HAP v0.11.1) (Homebridge FF17) with docker compose
- Docker image : latest (Image ID: fe4b3df0af0a)


### Process Supervisor

Docker (Mention image name in `Additional Context`)

### Additional Context

_No response_