Skysocks client bug when remote Pubkey set through hypervisor

[jdknives]

Describe the bug
When setting the PubKey of the remote skysocks server for skysocks-client through the hypervisor, the client does not start because it reports:

[2020-03-31T18:05:55+02:00] INFO [skysocks-client]: [2020-03-31T18:05:55.079622+02:00] FATAL []: Invalid server PubKey
[2020-03-31T18:05:55+02:00] WARN [skywire]: App stopped. app_name="skysocks-client" error="exit status 1"

Environment information:

• OS: Mac OS X

Steps to Reproduce
Steps to reproduce the behavior:

1. Setup two visors on separate machines or use integration env
2. Run manager UI
3. Set PubKey of remote for skysocks-client in UI
4. Start skysocks-client

Actual behavior

[2020-03-31T18:05:55+02:00] INFO [skysocks-client]: [2020-03-31T18:05:55.079622+02:00] FATAL []: Invalid server PubKey
[2020-03-31T18:05:55+02:00] WARN [skywire]: App stopped. app_name="skysocks-client" error="exit status 1"

Possible implementation
The error seems to stem from improper formatting of the skysocks-client args in config.

This is the config after setting PubKey through hypervisor (where proxy does not work):

	"args": [
				"-srv",
				"02985b7e04449cf33003396297f206bbbb3690d26e76c222f5f10d8e6791b16fd2"
			]

After changing the config manually it works:

"args": ["-srv","02985b7e04449cf33003396297f206bbbb3690d26e76c222f5f10d8e6791b16fd2"]

[jdknives]

Fixed by #288