Describe the bug
The spawned wander here points to a different binary than the one that started the current process and potentially does not read the original process's env vars or config params.

To reproduce
Steps to reproduce the behavior:

1. install wander<0.14.0 somewhere default, say where homebrew finds it
2. install wander@0.14.0 somewhere not in your $PATH
3. run wander and try to exec into an alloc, you should see it try to spawn the binary from 1 above

Expected behavior

1. exec may make use of the path returned by os.Executable instead of the string "wander" as well as adding existing env vars to the spawned process and a reference to the config file param to ensure the spawned process uses the same settings as the original running process.

Screenshots
If applicable, add screenshots to help explain your problem.

Please complete the following information:

• OS: Darwin,Linux
• Terminal: all
• Version: 0.14.0
• Configuration options used: env vars and .wander.yaml