fix: macos-14 (and assume later) runner(s) utilize M1 processor, causes build failures around pip

[jeremyary]

Is your feature request related to a problem? Please describe.

As evident here, the macos-latest / macos-14 image swaps to M1 processor and caused our CI actions to fail around pip install/upgrade. Until we handle this issue, we'll be pinned to macos-13.

Reason: tried: '/usr/local/opt/gettext/lib/libintl.8.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/gettext/lib/libintl.8.dylib' (no such file), '/usr/local/opt/gettext/lib/libintl.8.dylib' (no such file), '/usr/local/lib/libintl.8.dylib' (no such file), '/usr/lib/libintl.8.dylib' (no such file, not in dyld cache)

Describe the solution you'd like

Investigate failures around pip & determine code changes needed to enable latest & future macos runner versions.

[tokoko]

iirc, it was setup-python action that was failing. pip wasn't involved at that point.

[jeremyary]

Doh, wrong link from me as well, here's the link to the run log for further inspection