Use ~/.local/bin/poetry if it exists

[colindean]

As a better default or another step in resolution, let's check for ~/.local/bin/poetry and use it if it exists and ~/.local/bin isn't in the PATH, and of course, tell the user about the misconfiguration.

[colindean]

This comes off of #42: do the thing that works in most cases and tell the user that we're, uh, autocorrecting them.

[colindean]

A user I support was bit by this today.

The output here was that the user had manually installed Poetry via Homebrew at some point and was using that installation of Poetry. MPD doesn’t look for Poetry in a specific path… it just uses whatever poetry executable is first on the path.

Someone finally once again hit the reason why the Poetry devs discourage using the Homebrew formula and why MPD installs Poetry the way it does: when Poetry needs to manage its own environment, it sometimes cannot because the base Python that the venv points to went away.
That is, the (completely reasonable) way Homebrew upgrades Python may break existing Poetry venvs and require regenerating them.

The user needed to:

1. uninstall Poetry from Homebrew with brew uninstall poetry
2. run make deps to let MPD (re)install Poetry
3. Add Poetry’s export PATH=${HOME}/.local/bin:$PATH to ~/.zshrc

This problem would have been avoided if MPD always looked for $(HOME)/.local/bin/poetry first.

[colindean]

Related: python-poetry/poetry#10333