NSMgr adds NSE in registry with wrong URL

[Bolodya1997]

Issue

NSMgr adds NSE in registry with ListenOn[0] URL.

cmd-nsmgr/internal/manager/manager.go

Lines 105 to 108 in 196a358

	nsmMgr := &registry.NetworkServiceEndpoint{
	Name: configuration.Name + "#nsmgr",
	Url: configuration.ListenOn[0].String(),
	}

If it is a unix socket URL, NSE is unaccessible from the remote NSMgr.

Existing 'solution' of this problem is not working because it sets URL after it has been used for the NSMgr creation:

cmd-nsmgr/internal/manager/manager.go

Lines 201 to 203 in 196a358

	if listenURL.Scheme == tcpSchema {
	nsmMgr.Url = listenURL.String()
	}

Possible solution

Use URL with tcp scheme instead of ListenOn[0] URL.

What if there are multiple public URLs for different cases?

NSMgr can use multiple public URL, example:

1. unix socket - for communication between pods on single node
2. LAN IP address - for communication in domain
3. WAN IP address - for interdomain communication

Currently registry doesn't provide API to register NSE with both (2, 3) URLs, so NSE will be either unaccessible from the LAN, or from the Internet.