Volume not mounted if CONNECT_TO is set in ENVS

[LionelJouin]

The volume mounted in the NSC is hardcoded in the webhook, so if the CONNECT_TO environment variable is set to another directory than /var/lib/networkservicemesh, the NSC containers injected will not be able to communicate with the NSM API.

Steps to reproduce

1. Add the CONNECT_TO variable to the ENVS in the environment variables of the webhook

- name: NSM_ENVS
  value: NSM_CONNECT_TO=unix:///new-path/nsm.io.sock

2. Set the CONNECT_TO (or LISTEN_ON for nsmgr) environment variable for the other NSM components
3. Deploy NSM + webhook
4. Deploy an NSM application (NSC + NSE)

new-path is not mounted, so the NSC will not start.

[denis-tingaikin]

Be free to provide PR :)