stack/erp5: Fix NEO URL formatting for WCFS

The NEO/go commit kirr/neo@8c974485
changed the URL with which a NEO/go client can be loaded from

    // neo://name@master1,master2,...,masterN?options

to

    neo(s)://[credentials@]master1,master2,...,masterN/name?options

We need to apply this change in the NEO URL structure to instance-wcfs.cfg.in
to use WCFS with NEO storage.

Why?
====

The URL in instance-wcfs.cfg.in is finally send to wcfs binary, which
will open a NEO/go client with this URL via the "openClientByURL" function [1].
If the URL formatting instance-wcfs.cfg.in follows the old pattern,
NEO/go is unable to create a NEO/go client and may even raise an
exception [2], because information regarding NEO server is at the wrong
position of the URL.

---

[1] See https://lab.nexedi.com/kirr/neo/blob/87199da2b163c09ed3946b7ab9bb00a5b987d377/go/neo/client.go#L416-534
for openClientByURL.

[2] For instance when using the old pattern of putting the cluster name
in the "user" part, NEO/go will raise "credentials can be specified only
with neos:// scheme", because NEO/go reserves the "user" part for
encryption information,
see https://lab.nexedi.com/kirr/neo/blob/87199da2b163c09ed3946b7ab9bb00a5b987d377/go/neo/client.go#L449

---

/reviewed-by @kirr
/reviewed-on !1307
36 jobs for master in 0 seconds
Status Job ID Name Coverage
  External
passed Cloudooo.UnitTest-Master

00:07:37

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster

00:26:16

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster.Master

06:31:05

failed ERP5.StandaloneDeploymentScriptTest-Debian.Stretch

15:02:17

passed SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Buster

00:26:46

failed SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Stretch

15:02:04

passed SlapOS.Eggs.UnitTest-Master.Python2

00:14:43

passed SlapOS.Eggs.UnitTest-Master.Python3

00:16:20

passed SlapOS.KVM.ResilienceTest-Master

00:21:51

passed SlapOS.SlapRunner.ResilienceTest-Master

00:22:35

failed SlapOS.SlapRunner.ResilienceTest-Master.ERP5

00:20:11

passed SlapOS.SoftwareReleases.IntegrationTest-Master

05:54:47

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster

00:31:11

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster.Master

10:24:31

failed Wendelin.StandaloneDeploymentScriptTest-Debian.Stretch

15:02:12

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster

00:19:02

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster

00:26:28

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster

00:26:00

failed ERP5.StandaloneDeploymentScriptTest-Debian.Stretch

15:02:21

failed ERP5.StandaloneDeploymentScriptTest-Debian.Stretch

15:02:16

failed ERP5.StandaloneDeploymentScriptTest-Debian.Stretch

15:02:12

passed SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Buster

00:20:50

passed SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Buster

06:41:39

passed SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Buster

00:26:16

failed SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Stretch

15:02:00

failed SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Stretch

15:03:24

failed SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Stretch

15:02:00

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster

00:31:38

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster

00:31:46

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster

00:30:23

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster.Master

09:34:30

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster.Master

09:24:05

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster.Master

09:27:28

failed Wendelin.StandaloneDeploymentScriptTest-Debian.Stretch

15:02:03

failed Wendelin.StandaloneDeploymentScriptTest-Debian.Stretch

15:01:51

failed Wendelin.StandaloneDeploymentScriptTest-Debian.Stretch

15:01:59