pin to pip<22.1

[grlee77]

Description

investigating MacOS CI failures observed on main in #5198. I see that v0.19.x has setuptools pinned to <= 59.4. trying that on here as well to see if that resolves the issue.

update: The issue seems related to the recent release of pip 22.1 and not setuptools.

Checklist

• Docstrings for all functions
• Gallery example in ./doc/examples (new features only)
• Benchmark in ./benchmarks, if your changes aren't covered by an
  existing benchmark
• Unit tests
• Clean style in the spirit of PEP8
• Descriptive commit messages (see below)

For reviewers

• Check that the PR title is short, concise, and will make sense 1 year
  later.
• Check that new functions are imported in corresponding __init__.py.
• Check that new features, API changes, and deprecations are mentioned in
  doc/release/release_dev.rst.
• There is a bot to help automate backporting a PR to an older branch. For
  example, to backport to v0.19.x after merging, add the following in a PR
  comment: @meeseeksdev backport to v0.19.x
• To run benchmarks on a PR, add the run-benchmark label. To rerun, the label
  can be removed and then added again. The benchmark output can be checked in
  the "Actions" tab.

[jarrodmillman]

It would be good to merge this soon to eliminate this failure on new PRs.

[hmaarrfk]

What is the source of the issue. Is there a reference to an upstream issue. Why. Can we expect our users to install the software if we can't with the latest version of pip?