Revert "Fix GCP auth step for GitHub Actions workflows"

[damccorm]

Reverts #34624

This didn't fix the underlying issue - https://github.com/apache/beam/actions/runs/14446457300/job/40508116220 and took us from flaky to permared

[damccorm]

R: @Amar3tto

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

[Amar3tto]

I am not sure that it took us from flaky to permared because many last runs were almost permared (~0-1 out of 16 green).

[damccorm]

We were around 50% last week - https://github.com/apache/beam/actions/runs/14395319788 - it is interesting that it seems to be getting worse...

[Amar3tto]

I have an idea to add this command, it might help.

[damccorm]

Sounds good, feel free to give it a try. Please use https://github.com/apache/beam/blob/master/.github/workflows/README.md#how-to-fix-workflows-for-committers to test on a branch in the repo, should allow validating changes before the PR stage

[Amar3tto]

Even the gcloud auth activate-service-account command gives the same error (Invalid JWT Signature).
What do you think if we will try to move to workload_identity_provider or Artifact Registry approach ?
Also, seems like gcr.io is deprecated.

[damccorm]

I'm fine with that approach, could you try it out on a fork? We usually use https://console.cloud.google.com/iam-admin/serviceaccounts/details/107632624005655450554?e=13802955&invt=Abu0qQ&mods=dataflow_dev&project=apache-beam-testing

[Amar3tto]

It was found that the secret needs to be updated.

[Amar3tto]

I think we can close this PR

[damccorm]

Lets validate that the new approach works once the service account is updated first

[damccorm]

Ok, confirmed working in https://github.com/apache/beam/actions/runs/14516646976