m/test/launch: fail ROC on non-UNAVAILABLE errors

This makes RetrieveOwnerKeys fail fast in tests if some non-transient
(ie. non-UNAVAILABLE) error is encountered. I hit this while developing
something around the codebase and it took me way too long to figure out
why the e2e test was stalling.

This really begs doing a pass on all retry loops to make sure we don't
get stuck like this. Perhaps we should formalize this, too.

Change-Id: I048f5ac79802330f789e67ba316bc38f04d83331
Reviewed-on: https://review.monogon.dev/c/monogon/+/531
Reviewed-by: Lorenz Brun <lorenz@monogon.tech>
diff --git a/metropolis/test/launch/cluster/BUILD.bazel b/metropolis/test/launch/cluster/BUILD.bazel
index abcdc07..8e829df 100644
--- a/metropolis/test/launch/cluster/BUILD.bazel
+++ b/metropolis/test/launch/cluster/BUILD.bazel
@@ -28,6 +28,8 @@
         "@com_github_cenkalti_backoff_v4//:go_default_library",
         "@com_github_grpc_ecosystem_go_grpc_middleware//retry:go_default_library",
         "@org_golang_google_grpc//:go_default_library",
+        "@org_golang_google_grpc//codes:go_default_library",
+        "@org_golang_google_grpc//status:go_default_library",
         "@org_golang_google_protobuf//proto:go_default_library",
         "@org_uber_go_multierr//:go_default_library",
     ],