Name collision with pyvim on case-insensitive filesystems

Describe the bug

When working on a filesystem that does not support case-sensitivity and that also has the pyvim pip package installed, pip ends up dumping the files from the pyVim portion of pyvmomi into the same folder as the files for pyvim. This makes it so you are unable to correctly import from pyVim.

Reproduction steps

Testing was performed on Windows 10, using NTFS, with Python 3.9.13:

1. Install pyvim: pip install pyvim
2. Install pyvmomi: pip install pyvmomi
3. Launch Python: python
4. Attempt to import from pyVim module: from pyVim.connect import SmartConnectNoSSL, Disconnect
5. You receive the error: ModuleNotFoundError: No module named 'pyVim'
6. Attempt to import from pyvim module: from pyvim.connect import SmartConnectNoSSL, Disconnect
7. This works, but if you inspect the files in your site-packages directory, it is clear that the contents of pyvim and pyVim have been merged together by pip.

Expected behavior

I would expect that the components of pyvmomi have been named or distributed in such a way as to prevent name collisions with other publicly-available python packages.

Additional context

Perhaps this is a pip issue, however the overlap between the pyVim component of pyvmomi package and the pyvim package itself is unfortunate.

Reproduce the collision on Windows 10 with NTFS by installing pyvim and pyvmomi, then inspect the merged pyvim and pyVim contents in site-packages. Determine a distribution or naming change that preserves the documented pyVim imports without colliding with pyvim; done when both packages install and their imports work independently.