local .env file in project root supersedes global ~/.deepset-cloud/.env

Describe the bug
The CLI does not look for the global .env-file created using deepset-cloud login when a local .env-file in the project root is present. This means that CLI-commands cannot be executed as long as the project-.env file is present in the project-root.
The related error messages are not intuitively hinting at this conflict.

To Reproduce
Steps to reproduce the behavior:

1. create new project with .env-file in root folder and some example texts to upload to dP workspace
2. deepset-cloud login
3. deepset-cloud upload ./data/examples
4. the CLI raises WorkspaceNotDefinedError("Workspace name is not defined. Got ''. Enter the name of the workspace in workspace_name.")
5. deepset-cloud upload ./data/examples --workspace-name "default"
6. the CLI raises FailedToUploadFileException('Failed to upload file with status code 404. response was: {"detail":"Not Found"}')
7. moving the local .env-file out of the project root solves the issue

Expected behavior
Have CLI always default to using ~/.deepset-cloud/.env or choose during deepset-cloud login whether to use global or local .env-file

Screenshots

Start with the deepset-cloud login and deepset-cloud upload entry points and reproduce the conflict between the project .env file and ~/.deepset-cloud/.env. Trace which environment source is selected and how the workspace and upload errors are produced. Done means the global credentials remain usable with a project-root .env file, with an unambiguous behavior for choosing the environment source.