Reintegrate wireguard in zoslight/zos4

[Eslam-Nawara]

Is your feature request related to a problem? Please describe

we need to reintegrate wireguard again in zos4

[Eslam-Nawara]

WIP

Working on adding wireguard back to zos4.

• added back the list_wg_ports endpoint to zos_api
• updated the resource module to have back the network resource and network ip range
• updated netlight create function to handle setting up wireguard

[Eslam-Nawara]

WIP

• reintegrated wireguard in zos4
• updated vm-light to be able to access it with wg ip
• deployed a network and a container with wireguard access and was able to reach the network and ssh to the container
• I used this configurations to to run wg

[Interface]
Address = 100.64.1.2/32
PrivateKey = vOGYXS85T8w6irYzV9x9CYcBVX9bR4yZxKcP9T1msAM=

[Peer]
PublicKey = cYvKjMRBLj3o3e4lxWOK6bbSyHWtgLNHkEBxIv7Olm4=
AllowedIPs = 10.1.1.0/24, 100.64.1.1/32
PersistentKeepalive = 25
Endpoint = 192.168.123.32:3011

• Used network light with this configurations

zos.NetworkLight{
Subnet:         gridtypes.MustParseIPNet("10.1.1.0/24"),
NetworkIPRange: gridtypes.MustParseIPNet("10.1.0.0/16"),

WGPrivateKey: wgKey,
WGListenPort: 3011,

Peers: []zos.Peer{
	{
		Subnet:      gridtypes.MustParseIPNet("10.1.2.0/24"),
		WGPublicKey: "4KTvZS2KPWYfMr+GbiUUly0ANVg8jBC7xP9Bl79Z8zM=",

		AllowedIPs: []gridtypes.IPNet{
			gridtypes.MustParseIPNet("10.1.2.0/24"),
			gridtypes.MustParseIPNet("100.64.1.2/32"),
		},
	},
},
Mycelium: zos.Mycelium{
	Key: mycKey,
},

Now I'm able to join the network

And can ssh to the container using wg ip