`meltano install` doesn't install new version of plugin when `pip_url` is changed but package version stayed the same
meltano install just runs
pip install <pip_url>, which does not actually install the new package unless the version specified in
setup.py has changed.
This is unexpected if a user wants to switch from the canonical
<pip_url> to their own fork, since
meltano install output will not give any indication that the plugin wasn't actually upgraded.
We can make
meltano install smarter and detect
pip_url changes (perhaps by storing the current pip_url in a file alongside the venv?), and/or we can add a
--force flag to
meltano install to ensure all taps are reinstalled.
Or we can simply always pass pip's
--force-reinstall flag: https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-force-reinstall