Resolve import name collisions intelligently

In some cases (e.g. #138), an import name can point to multiple packages and result in outputting a suboptimal or incorrect requirement. `pipreqs` could make better decisions here using some heuristics such as existing requirements files, currently installed libraries, or external popularity / usage statistics from PyPI or GitHub. This would also require the mapping file to support one-to-many mappings.