buildkite: use GCP OIDC (backport #13856)

[mergify]

Proposed commit message

• Use GCP OIDC to copy the logs to the private storage.
• Use gcloud instead of gsutil (so it honours the Env variables)
• Tear-down is now managed by the BK plugin itself.

Test

See the ci build

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Relates to elastic/elastic-package#2569

Screenshots

---

This is an automatic backport of pull request #13856 done by [Mergify](https://mergify.com).

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 1f4bf06

Failed CI Steps

• Check integrations mysql
• Check integrations ping_federate

History

cc @v1v

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

Package fortinet_fortiedr 👍(0) 💚(0) 💔(1)

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
log	964.32	532.2	-432.12 (-44.81%)	💔

Package microsoft_dhcp 👍(0) 💚(0) 💔(1)

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
log	11764.71	9174.31	-2590.4 (-22.02%)	💔

To see the full report comment with /test benchmark fullreport

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube