chore: manually updating puppeteer and google-github-actions/auth action to v1.1.1 from forked renovate

[pattishin]

Description

Origin PRs:

• chore(deps): update google-github-actions/auth action to v1.1.1 #3206
• chore(deps): update dependency puppeteer to v20 #3197

Last sentence in error above from PR 3206 , google-github-actions/auth seems to error out if job is initiated via forked version. Updating this manually.

Checklist

• I have followed guidelines from CONTRIBUTING.MD and Samples Style Guide
• Tests pass: npm test (see Testing)
• Lint pass: npm run lint (see Style)
• These samples need a new API enabled in testing projects to pass (let us know which ones)
• These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
• This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
• This sample adds a new sample directory, and I created GitHub Actions workflow for this sample
• This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
• Please merge this PR for me once it is approved

[pattishin]

Looking into dialogflow-cx test failure.

[kweinmeister]

Hi @pattishin , thanks for taking care of this!

Just FYI, the way CI is currently configured, we can ignore these pull_request failures if the matching pull_request_target is passing.

The pull_request_target actually does setup permissions properly on forks. However, we should manually inspect any forked PRs for security reasons. If it looks good, we can then apply the actions: force run label to trigger the PR target check.

We have an open issue #2891 filed to cleanup this workflow.

[kweinmeister]

The dialogflow-cx error looks like an unrelated flaky test, but I do think we need to fix this blocking issue: #3158 to make sure the Puppeteer upgrade is working correctly. Notice the error on run/websockets.

[pattishin]

Thanks @kweinmeister! Checking it out 👍🏼