vpn: write test to check that there's no whitespace in openvpn command invocation
while debugging a problem with options suddently not being recognized, I found a bug in the concatenation of options for composing the openvpn command line invocation.
part of the problem is how messy this process currently is. I need to streamline the command generation, and it has to be more clear which options are added by bitmask-root or bitmask-helper in osx.
an idea to test this could be to have an auxiliary function that invokes the routine in bitmaksk-root that composes the command, ant test that together with the particular platform launcher.