Prioritize the virtualenv over venv in presence of both packages

The venv packages cannot handle the system interpreter being a virtualenv in itself - though this is not incommon. The commit just prioritizes virtualenv and spits out warning if a user runs into the above scenario.

This merge request supersedes !559 (closed) after @smuething dislike for the former.