v1.4.0

Changes to how the path to orbit is handled

Previous versions stored the full path to the executable, which causes issues in installations where the path may be version-dependent. Starting with this version, it stores orbit by default and relies on the user having systemd's PATH correctly configured. Alternatively, there is now an orbit_bin top-level configuration that may be used to specify a full path to the binary/shim.

Adjusts doctor checks for this case and de-sloppified a bit.

Full Changelog: v1.3.1...v1.4.0