Upper bound on noarch python packages

### Your question:

I would like to suggest we start adding an upper bound on noarch python packages.

The reason is that the python standard library has been in flux for a while and this is causing packages that declare themselves as `noarch: python` to have to retroactively apply repodata patches when a new version of python comes out.

It would be great if in addition to the lower bound, we also had infrastructure that would trigger a rebuild for python packages that are noarch when a new version comes out.

The lastest problem we faced is: is with:
- https://github.com/googleapis/proto-plus-python/pull/329/files#diff-11135ba0cd87468dca27e3a55d229e49647ff84f55d04301239ead576bd25743R61
which is included in their 1.22.2 release https://github.com/googleapis/proto-plus-python/releases/tag/v1.22.2

which caused problems for:
https://github.com/conda-forge/google-cloud-pubsub-feedstock/pull/54

It would have been great if versions of proto-plus-python were limited, by our infrastructure, to 3.6->3.10 until a rebuild is explicitly triggered for 3.11 putting the responsibility in the package maintainer's hands.