bug(libwaku): using port 0 for tcp does not automatically allocate a port

[richard-ramos]

Problem

While using waku-rust-bindings, something that was reported by @seemenkina is that using port 0 does not longer automatically find a free port. This is because the newer version of the rust bindings no longer use go-waku for the waku functionality but nwaku instead.
Discussing with @gabrielmer, it seems that this functionality is there in nwaku, but it seems that it is not being used on libwaku.

Related: #2359

Impact

Users of libwaku will need to manually specify a port number. This might lead to a bad developer experience as well as issues on CI in case of flaws in the logic the developer uses to find a free port