Fix broken pip installer by forcing it to detect macOS 11 as 11.0 and not 10.16

[joshuacwnewton]

Description

This was a really weird bug to investigate!! General background info references:

• https://eclecticlight.co/2020/07/21/big-sur-is-both-10-16-and-11-0-its-official/
• packaging does not know that macOS 10.16 and 11.0 are the same pypa/packaging#497 (comment)
• Issue with NumPy, macOS 11 Big Sur, Python 3.9.1 Does pipenv not use the latest pip? pypa/pipenv#4564 (comment)

Specific to onnxruntime:

• pip doesn't install latest version of onnxruntime microsoft/onnxruntime#17166
• In a fresh miniconda environment, pip detects the macOS version number as 10.16, causing the new 1.17.0 onnxruntime wheels to not be found microsoft/onnxruntime#19371

The above issue has only become relevant for SCT because one of its dependencies, onnxruntime switched to wheels that specify macosx_11_0 in the wheel's name instead of the previous macosx_10_15. So, we need the compatibility fix to install the newest onnxruntime wheels, at least until pip fixes this upstream by vendoring a newer version of packaging:

• Upgrade the vendored packaging to 22.0+ pypa/pip#11715

Linked issues

Fixes #4352.

[mguaypaq]

Wow! This macOS 10.16 == 11.0 thing is such a weird version number hack on the part of Apple. Thanks for tracking it down, and for all the references!