OSX Monterey removes python2 in default system path, and as a result, causing bazel 4.2.x iOS target build failure due to "python" not found error. Upgrading to bazel 5.x appears fixing the issue. However, this is dependent on gRPC c-core's bazel version upgrade
Investigate possible workaround with using bazel 4.2.1 on Mac OSX Monterey for iOS bazel tests.
OSX Monterey removes python2 in default system path, and as a result, causing bazel 4.2.x iOS target build failure due to "python" not found error. Upgrading to bazel 5.x appears fixing the issue. However, this is dependent on gRPC c-core's bazel version upgrade
Investigate possible workaround with using bazel 4.2.1 on Mac OSX Monterey for iOS bazel tests.
related PR discussion https://github.com/grpc/grpc/pull/29599
cc @HannahShiSFB