Try using `bazelbuild/setup-bazelisk` everywhere.

This should hopefully mean that the `bazel`
command found first in the path is actually
Bazelisk.

Revert various previous attempts to get all
this working...

Change-Id: I9a6267aff334de3dc55c7333d83e67ad2ad4ef05
Reviewed-on: https://code-review.googlesource.com/c/re2/+/61610
Reviewed-by: Perry Lorier <perryl@google.com>
Reviewed-by: Paul Wankadia <junyer@google.com>
5 files changed