Update pyproject.toml for Python 3.11 support and to fix 32-bit Windows pinnings

[grlee77]

Update

This PR has been revised to only make some minor updates to pyproject.toml as the 3.11 testing on CI was since added separately in #6566. The original description is still below

Description

This PR adds a test case with Python "3.11-dev" (currently 3.11.0-rc.2) to the linux and MacOS test matrices. For now, extra pip flags are added to help find nightly 3.11 wheels for SciPy and Matplotlib. NumPy, Cython and PyWavelets have Python 3.11 wheels up on PyPI itself.

Aside from the 3.11-specific changes there are two additional improvements to pyproject.toml here:

• updated NumPy version pinning for Python 3.10. This would allow us to restore the win32 wheels that are currently skipped on 3.10 in our wheel building script
• upper version pin on setuptools to protect against future backward-incompatible changes

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.

[grlee77]

Thanks @jarrodmillman for adding the Python 3.11 tests in #6566. I think there are still some pyproject.toml changes here that we probably want, so I have renamed the PR accordingly.

• update NumPy pinnings to fix Windows 32-bit and Python>3.11 behavior
• add an upper bound to setuptools (just pinned to the current version as it still seems to work for me)

Note that the setuptools pin is only for the version used during the build and is not a restriction on users installing scikit-image.

[mkcor]

@jarrodmillman shouldn't we request your review of this PR, in the perspective of the 0.20 release? ❤️

[jarrodmillman]

I am going to merge this and rebase PR #6581 on it.

[mkcor]

Thank you, @jarrodmillman!