virtualenv is displayed incorrectly for poetry and conda

[chvolkmann]

When using poetry to manage virtualenvs, this is what tide displays

The virtualenvs should be the name of my virtualenv.

echo $VIRTUAL_ENV
/home/user/.cache/pypoetry/virtualenvs/myproject-j_EVlIcP-py3.8

So the venv should be displayed as myproject-j_EVlIcP-py3.8 or myproject. Something similar could be implemented for conda users. Here, CONDA_DEFAULT_ENV should be used instead of VIRTUAL_ENV.

I'll cook up a pull request for _tide_item_virtual_env.fish in a bit!

[IlanCosman]

This is the intended behavior, though perhaps it should be changed.

[IlanCosman]

@chvolkmann I've made the virtual_env item a bit smarter, so that poetry won't have this issue. Feel free to open a new issue for conda 😄