Use current working directory when searching for .env

[laserb]

The .env was only found if it is placed next to the virtualenv.
If the virtualenv is in another directory, then the .env was ignored and commodore failed.
Fix it by searching the .env in current directory.

Checklist

• Keep pull requests small so they can be easily reviewed.
• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking, dependency
  as they show up in the changelog

[simu]

LGTM.

Just to clarify the issue description: from what I can tell, the issue doesn't stem from the relative location of the virtualenv in respect to the .env file but rather the relative location of the Commodore package compared to the .env file, since the old implementation works fine for me with .env in /home/simon/work/syn/commodore and the Poetry virtualenv in /home/simon/.cache/pypoetry/virtualenvs/commodore-mfZDsTMQ-py3.9.

[laserb]

Yes, the relative location of the .env and the commodore.cli is important. dotenv searches in the parent folders of commodore.cli. It fails if you do not run it with poetry run. I.e. install it with poetry install or pip.