CI: use pipx and build to simplify and remove a workaround (2)
- CI: use pipx and build to simplify and remove a workaround
- ci: drop setup-python, show build version

- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit) for how to run them
- [ ] whatsnew entry

This cleans up the SDist build slightly. First, it uses PyPA's "build" instead of directly calling `setup.py`, which will respect PEP 518 requirements and avoids the workaround of installing NumPy to be able to run setup.py. It also uses pipx to avoid needless setup; PyPA's pipx is provides as a first-class package manager on GitHub Actions (and Azure, they share images).

Repushing #43157. No changes (except rebasing). I think the next step was to make sure the local SDist builds were brought in sync with this.

> I think the next step was to make sure the local SDist builds were brought in sync with this.

probably should do that before making the changes to the ci here in pandas which is just to catch problems early. Thanks @henryiii for the PR. will close this to clear the queue.

As mentioned above and https://github.com/pandas-dev/pandas/pull/43157#issuecomment-1046224160, the sdist build on ci should replicate the release process to catch issues early so any changes should probably be made to https://github.com/pandas-dev/pandas-release in the first instance.

Given that there is active discussion on using cibuildwheel and pandas could soon be migrating  https://github.com/pandas-dev/pandas/issues/44027#issuecomment-1068625999, I think I am happier not to make any changes to the release process for now.