bug: nwaku<->gowaku interop tests started failing at filter subscription

[fbarbu15]

Problem

Starting with this night I see all those filter tests failures in nwaku<->gowaku tests.
On nwaku<->nwaku tests there is only one failure

To reproduce

1. Start nodes like this

docker run -i -t -p 12130:12130 -p 12131:12131 -p 12132:12132 -p 12133:12133 -p 12134:12134 wakuorg/nwaku:latest --listen-address=0.0.0.0 --rest=true --rest-admin=true --websocket-support=true --log-level=TRACE --rest-relay-cache-capacity=100 --websocket-port=12132 --rest-port=12130 --tcp-port=12131 --discv5-udp-port=12133 --rest-address=0.0.0.0 --nat=extip:172.18.228.41 --peer-exchange=true --discv5-discovery=true --cluster-id=3 --nodekey=adbe56daa603d0d8e9d4ae25ad82e2e45ac16e4e3ed2efc37cbfcf6c93fce69c --shard=0 --metrics-server=true --metrics-server-address=0.0.0.0 --metrics-server-port=12134 --metrics-logging=true --relay=true --filter=true

docker run -i -t -p 7981:7981 -p 7982:7982 -p 7983:7983 -p 7984:7984 -p 7985:7985 wakuorg/go-waku:latest --listen-address=0.0.0.0 --rest=true --rest-admin=true --websocket-support=true --log-level=DEBUG --rest-relay-cache-capacity=100 --websocket-port=7983 --rest-port=7981 --tcp-port=7982 --discv5-udp-port=7984 --rest-address=0.0.0.0 --nat=extip:172.18.239.216 --peer-exchange=true --discv5-discovery=true --cluster-id=3 --nodekey=abd8cb020bae15fce3affa8dae772baabbf01fbade4a7186d7fe9eb5f8572bc5 --min-relay-peers-to-publish=1 --rest-filter-cache-capacity=50 --peer-store-capacity=10 --relay=false --discv5-bootstrap-node=enr:-L24QA39xcq7yUnwXSDq5xSBk3xd0011DeWsrsFtxySwC4uBCzNckgLDZ_Mqk7TtrtstzA6wAnf8hXDMElnpIX_y0a8CgmlkgnY0gmlwhKwS5CmKbXVsdGlhZGRyc5YACASsEuQpBi9jAAoErBLkKQYvZN0DgnJzhQADAQAAiXNlY3AyNTZrMaECpQTrl7pHDJvmSsd9PkmMk9YcTngahneMes6jNLRNhi-DdGNwgi9jg3VkcIIvZYV3YWt1MgU --filternode=/ip4/172.18.228.41/tcp/12131/p2p/16Uiu2HAm6XqbrDvqghuKqaGFaPPwwE1NS8z4ETPb1omFQF9RRZ2v --pubsub-topic=/waku/2/rs/3/1

2. Connect them :
   curl -v -X POST "http://127.0.0.1:7981/admin/v1/peers" -H "Content-Type: application/json" -d '{"multiaddr": "/ip4/172.18.228.41/tcp/12131/p2p/16Uiu2HAm6XqbrDvqghuKqaGFaPPwwE1NS8z4ETPb1omFQF9RRZ2v", "protocols": ["/vac/waku/relay/2.0.0"], "shards": [0, 1, 2, 3, 4, 5, 6, 7, 8]}'
3. Filter subsribe:
   curl -v -X POST "http://127.0.0.1:7981/filter/v2/subscriptions" -H "Content-Type: application/json" -d '{"requestId": "d797d137-1405-4e3d-89aa-82e3e0c0b92e", "contentFilters": ["/test/1/waku-filter/proto"], "pubsubTopic": "/waku/2/rs/3/1"}'

Expected behavior

Should work

Actual behavior

Fails with subscription failed
In logs I see "SERVICE_UNAVAILABLE: addSubscription no connection to peer: 16U*Ug76iF\"

Screenshots/logs

node1.log
node2.log