Identity REST API endpoint returns 0.0.0.0 address
**Describe the bug**
Currently the `/eth/v1/node/identity` REST API endpoint returns incorrect multiaddress under `p2p_addresses`:
```
jakubgs@linux-01.ih-eu-mda1.nimbus.sepolia:~ % c -s 0:9311/eth/v1/node/identity | jq '.data | { p2p_addresses, discovery_addresses }'
{
  "p2p_addresses": [
    "/ip4/0.0.0.0/tcp/9011/p2p/16Uiu2HAmQEmCoEfKQ7ZdPyw1vkMYPLfosfksRUJwssvyDzAosGgm"
  ],
  "discovery_addresses": [
    "/ip4/185.181.230.77/udp/9011/p2p/16Uiu2HAmQEmCoEfKQ7ZdPyw1vkMYPLfosfksRUJwssvyDzAosGgm"
  ]
}
```
As can be seen the `discovery_addresses` is correctly using the known public IP address - most probably thanks to the correct value of the `--nat=extip:...` flag - while `p2p_addresses` returns `0.0.0.0`.

**Additional context**
Present currently for all 4 main branches:
```
jakubgs@linux-01.ih-eu-mda1.nimbus.sepolia:~ % for port in $(seq 9311 9314); do c 0:$port/eth/v1/node/identity | jq -c .data.p2p_addresses; done
["/ip4/0.0.0.0/tcp/9011/p2p/16Uiu2HAmQEmCoEfKQ7ZdPyw1vkMYPLfosfksRUJwssvyDzAosGgm"]
["/ip4/0.0.0.0/tcp/9012/p2p/16Uiu2HAm5rcnvjSbXMtzosDnGBsgwi5REfxCNCjeqcYDnHf86XsF"]
["/ip4/0.0.0.0/tcp/9013/p2p/16Uiu2HAmCDZ2qDxdoRYdYGYentnSndWfTYuSSh9jzzK3Qc6QGd1q"]
["/ip4/0.0.0.0/tcp/9014/p2p/16Uiu2HAmGXdiCU2VX9GpuTq3GPm28gBncaBLWEcN8MZaskXcYhYb"]
```