Auth via `wb-auth` breaks once monitored network added to `wb-auth` service

[YuryHrytsuk]

Description

After monitored network is added to wb-auth service, services get stuck in connecting state. Network calls return 500

Vendor services have the same problem when configured to auth via wb-auth (500 page is shown)

Related PR/s

• Probably makes service stuck in connecting state 🐛 fixes directorv2: Use wb-auth as forwardauth for dynamic services osparc-simcore#8139
• Blocks Add wb-auth simcore service #1146

[YuryHrytsuk]

I think this is what happens https://forums.docker.com/t/docker-swarm-dns-resolution-was-multiple-networks/137488

[YuryHrytsuk]

This only happens when network is added "on-the-fly" via Portainer. When wb-auth is deployed with docker stack yaml, it works fine

Read more https://forums.docker.com/t/docker-swarm-dns-resolution-was-multiple-networks/137488/9