fix using wrong pip module for installing the pip package

[benjaminum]

This PR ensures that the install-pip-package target uses the pip module that matches the python environment.

---

This change is 

[update-docs]

Thanks for submitting this pull request! The maintainers of this repository would appreciate if you could update the CHANGELOG.md based on your changes.

[yxlao]

LGTM as long as the test is passing.

There seems to be some issue with Windows + CUDA, could you double-check that?

[benjaminum]

@yxlao It seems to be related to the fmt library. Error messages do not make sense. Could be a duplicate definition.
#3456 has similar errors and also does have changes to CMake scripts. Seems like a small change to a cmake script can trigger this.

[stotko]

@yxlao It seems to be related to the fmt library. Error messages do not make sense. Could be a duplicate definition.
#3456 has similar errors and also does have changes to CMake scripts. Seems like a small change to a cmake script can trigger this.

The error in #3456 occurred after rebasing to the latest master branch changes and addressing some minor comments. First. I thought that this could be related to the latter part, but it now looks more like a regression coming from master in GitHub Actions' Windows CI image.

[stotko]

After checking a few things, this seems like a regression in GitHub Actions' Windows CI image. They recently upgraded Visual Studio 2019 from 16.9 to 16.10 which seems to introduce these error when compiling with CUDA.

Reference: actions/runner-images#3485

[benjaminum]

After checking a few things, this seems like a regression in GitHub Actions' Windows CI image. They recently upgraded Visual Studio 2019 from 16.9 to 16.10 which seems to introduce these error when compiling with CUDA.

Reference: actions/virtual-environments#3485

This makes sense. I did re-run the Win CI for merged PR #3521 (basically master) and we get the same errors.