Configured binary might not be used if one already exists in the default path

If you configure the binary path, but then you already have a binary in the default path, and the default path matches the server but the configured path does not, it will use the default path.

While in some sense this makes sense (the default path one is a "better" match because it matches the server version) it feels unexpected to me that you can configure the path and it uses something else. In one particular case, we *want* a different version because the latest version of the cli has a bug.

Additionally, feels like the "fall back to data directory" setting should affect this, but it does not. Should specify it only affects when it tries to *download* the binary.