allow spaces within Unix domain socket paths (ControlPort and SocksPort)
We are adding Unix domain socket support to Tor Launcher and Torbutton (see legacy/trac#14270 (moved) and its child tickets). But there does not seem to be a way to configure a Unix domain socket path that contains a space character (spaces within path names are somewhat common on macOS at least).
When I include a space in a ControlPort or SocksPort directive, it is interpreted as the separator that precedes the flags.
If there is a way to do this, please tell me how. If there is not currently a way, then please give me a hint as to how to fix it.