Repository: pykeen/pykeen
Issue: pip installation broken (1.8.1)
Root cause: External Dependency Breakage

### Describe the bug

It seems the package has a dependency on a deprecated version of the scikit-learn. There is a workaround to use an older version of scikit-learn but that would break other packages that already use new scikit-learn


### How to reproduce

```shell
pip install pykeen==1.8.1
Defaulting to user installation because normal site-packages is not writeable
Looking in indexes: http://example.com/repository/avt-pypi-proxy/simple
Collecting pykeen==1.8.1
  Using cached http://example.com/repository/avt-pypi-proxy/packages/pykeen/1.8.1/pykeen-1.8.1-py3-none-any.whl (630 kB)
Collecting dataclasses-json (from pykeen==1.8.1)
  Using cached http://example.com/repository/avt-pypi-proxy/packages/dataclasses-json/0.6.7/dataclasses_json-0.6.7-py3-none-any.whl (28 kB)
Requirement already satisfied: numpy in /home/STRIKETECH/jnunez/.local/lib/python3.7/site-packages (from pykeen==1.8.1) (1.21.6)
Requirement already satisfied: scipy>=1.5.0 in /home/STRIKETECH/jnunez/.local/lib/python3.7/site-packages (from pykeen==1.8.1) (1.7.3)
Requirement already satisfied: click in /home/STRIKETECH/jnunez/.local/lib/python3.7/site-packages (from pykeen==1.8.1) (8.1.7)
Collecting click-default-group (from pykeen==1.8.1)
  Using cached http://example.com/repository/avt-pypi-proxy/packages/click-default-group/1.2.4/click_default_group-1.2.4-py2.py3-none-any.whl (4.1 kB)
Collecting sklearn (from pykeen==1.8.1)
  Using cached http://example.com/repository/avt-pypi-proxy/packages/sklearn/0.0.post12/sklearn-0.0.post12.tar.gz (2.6 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [15 lines of output]
      The 'sklearn' PyPI package is deprecated, use 'scikit-learn'
      rather than 'sklearn' for pip commands.

      Here is how to fix this error in the main use cases:
      - use 'pip install scikit-learn' rather than 'pip install sklearn'
      - replace 'sklearn' by 'scikit-learn' in your pip requirements files
        (requirements.txt, setup.py, setup.cfg, Pipfile, etc ...)
      - if the 'sklearn' package is used by one of your dependencies,
        it would be great if you take some time to track which package uses
        'sklearn' instead of 'scikit-learn' and report it to their issue tracker
      - as a last resort, set the environment variable
        SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL=True to avoid this error

      More information is available at
      https://github.com/scikit-learn/sklearn-pypi-package
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
```

### Environment

```shell
Python 3.10.4 (main, Mar 31 2022, 08:41:55) [GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
```

```shell
Requirement already satisfied: scikit-learn in /opt/Anaconda3-2019.10/lib/python3.7/site-packages (0.21.3)
Requirement already satisfied: numpy>=1.11.0 in /opt/Anaconda3-2019.10/lib/python3.7/site-packages (from scikit-learn) (1.17.2)
Requirement already satisfied: scipy>=0.17.0 in /opt/Anaconda3-2019.10/lib/python3.7/site-packages (from scikit-learn) (1.3.1)
Requirement already satisfied: joblib>=0.11 in /opt/Anaconda3-2019.10/lib/python3.7/site-packages (from scikit-learn) (0.13.2)
```


### Additional information

```shell
cat /etc/redhat-release
Fedora release 29 (Twenty Nine)
```


### Issue Template Checks

- [X] This is not a feature request (use a different issue template if it is)
- [X] This is not a question (use the [discussions](https://github.com/pykeen/pykeen/discussions/new) forum instead)
- [X] I've read the text explaining why including environment information is important and understand if I omit this information that my issue will be dismissed

Hi @jnunezgts ,

you are trying to install an old version of `pykeen`. This issue is fixed in newer versions.

No idea why I copied and pasted an old version. This worked out of the box:

```shell
pip install pykeen==1.10.2
```

Thanks for looking into this.