buildscripts: Use the Kokoro shared install lib from the new repo (v1.57.x backport)

[sergiitk]

Backport of #10757 to v1.57.x.

Source: https://github.com/grpc/grpc/blob/4f7ead2c7b7b82ad80799bbfa482184991dcd346/tools/internal_ci/linux/grpc_xds_k8s_install_test_driver.sh
New repo: https://github.com/grpc/psm-interop
New path: .kokoro/psm_interop_kokoro_lib.sh

Ref grpc/psm-interop#16.

[YifeiZhuang]

macos tests are failing/aborted, fusion, maybe due to limited executor in the cluster pool.

15:31:25 PST] Build #10 enqueued, logging initialized.
[15:31:25 PST] Test Fusion Url: [http://fusion2/ci/kokoro/prod%3Agrpc%2Fjava%2Fv1.57.x%2Fpresubmit%2Fmacos/activity/a5da509f-32d4-4dcb-b132-1707d11c7743](https://www.google.com/url?q=http://fusion2/ci/kokoro/prod%253Agrpc%252Fjava%252Fv1.57.x%252Fpresubmit%252Fmacos/activity/a5da509f-32d4-4dcb-b132-1707d11c7743&sa=D) 
[15:48:32 PST] Your build has been queued for 17 minutes and has not yet been scheduled. This build is running on a custom pool so there could be a configuration error causing the blockage. If builds are just taking too long and are not completely stuck, try to increase the executor count. This may get the builds to run faster. To debug configuration errors, check out [go/kokoro-executor-errors](http://goto.google.com/kokoro-executor-errors) or run this command:

$  stubby call blade:kokoro-api KokoroApi.GetExecutorErrors 'cluster: MACOS_EXTERNAL, pool: "macsvc-catalina"'

Here are some recent executor errors on MACOS_EXTERNAL macsvc-catalina that may help:
[12/15 15:41:02] Failed to create lease for executor 273894967
[12/15 15:40:59] Failed to create lease for executor 1840771917
[12/15 15:40:54] Failed to create lease for executor 1344662813
[18:48:39 PST] Build ran too long and is now being cancelled.
[18:48:40 PST] This build was finished while in a QUEUED state. Now finalizing the invocation.

[ejona86]

cl/560839757 only applied from that point forward. The older branches (purposefully) didn't get it because we didn't want to change the minimum Mac OS version for those old branches. Now that the older pool is shut down, they are just broken.

It'd probably be fair to change the older branches to use Big Sur. And also change master to use Monterey, because Big Sur hasn't been getting updates from Apple since September.

[ejona86]

Alternatively, I could turn off the Macos requirement.

[YifeiZhuang]

cl/560839757 only applied from that point forward. The older branches (purposefully) didn't get it because we didn't want to change the minimum Mac OS version for those old branches. Now that the older pool is shut down, they are just broken.

It'd probably be fair to change the older branches to use Big Sur. And also change master to use Monterey, because Big Sur hasn't been getting updates from Apple since September.

cl/592028105