pipreqs requiring asposestorage==1.0.2 without reason

Hello,
we found a bug in pipreqs: if we import a module called `models`, then it will create a `requirements.txt` file containing `asposestorage==1.0.2`.

To reproduce:
1. Create a file called `my_module.py` containing this code:
```
import models

if __name__ == "__main__":
pass
```
2. run `pipreqs .` in the folder containing this module (you don't need to have a `models.py` file in the folder!).

Result: a `requirements.txt` file is created with this content:
```
asposestorage==1.0.2
```

Versions:
`pipreqs --version` --> 0.4.13
`Python 3.11.7`

Possible explanation:
this file contains a mapping: models --> asposestorage (https://github.com/bndr/pipreqs/blob/cd3f437689a9f27c8045de5126dcbe004d2ceebe/pipreqs/mapping#L793) not sure how it is used but I think that `models` is a quite common module names in these AI days so not sure there should be a default sketchy library imported for models.

Start with the mapping entry at pipreqs/mapping#L793 and reproduce the report using a module that imports `models` with Python 3.11.7 and pipreqs 0.4.13. Determine how that mapping produces the requirement, then verify that the reproduction no longer creates `asposestorage==1.0.2` in requirements.txt.

Written by the indexing model from the issue text.