Display output of start-gke-env.sh (#7454)

### Description of the change

Avoid piping the output of the script to investigate an error in CI.

### Benefits

N/A

### Possible drawbacks

N/A

### Applicable issues

N/A

### Additional information

N/A

Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>

.github/workflows/gke_e2e_tests.yaml

@@ -102,7 +102,7 @@ jobs:
       - name: Start GKE environment
         run: |
           set -euo pipefail
-          ./script/start-gke-env.sh "${ESCAPED_GKE_CLUSTER}" "${GKE_ZONE}" "${GKE_VERSION}" "${GKE_ADMIN}" "${GKE_RELEASE_CHANNEL} "${ALLOW_GKE_VERSION_FALLBACK}" > /dev/null
+          ./script/start-gke-env.sh "${ESCAPED_GKE_CLUSTER}" "${GKE_ZONE}" "${GKE_VERSION}" "${GKE_ADMIN}" "${GKE_RELEASE_CHANNEL} "${ALLOW_GKE_VERSION_FALLBACK}"
       - # TODO(castelblanque) Unify shared resources with kubeapps-local-dev-users-rbac.yaml that only applies to Kind clusters
         name: Apply customizations to GKE cluster
         run: |