Recommend dependency version management tooling based on use case

Similar to the problem in https://github.com/pypa/python-packaging-user-guide/issues/118 with regards to virtual environment management, our current tooling recommendations don't provide a pointer to higher level dependency version management tools like pipenv or pip-tools, they only refer to pip itself.

While we don't want to overwhelm people with choice, I think we're currently doing folks a disservice by letting them think pip is all there is, rather than guiding them towards more opinionated higher level tooling:

• pipenv: web application development (and potentially other forms of application development)
• pip-tools: general application development (useful when pipenv doesn't align with your needs)
• conda: language-independent cross-platform package (useful when you have extensive external dependencies)

Commencez par lire les recommandations actuelles concernant les outils ainsi que l’issue 118 correspondante de python-packaging-user-guide. Déterminez où pip est actuellement présenté et mettez à jour cette documentation afin d’orienter les lecteurs vers pipenv, pip-tools ou conda selon leur cas d’utilisation. La tâche sera terminée lorsque les recommandations seront claires sans submerger les lecteurs de choix inutiles.