Buildkite: Increase build agent disk to 200 GB

[reakaleek]

What

Bumps diskSizeGb from 150 → 200 GB on GCP build agents in both the full build and PR build pipelines.

Why

Build is failing during tar -x while extracting the kibana git archive, likely due to running out of disk space. The 50 GB increase provides headroom for the git bare clone + working copy extraction + build output that all live on disk simultaneously.

How

One-line change to diskSizeGb in each pipeline YAML.

Test plan

• Trigger a PR build against a kibana PR and confirm the tar extraction step completes successfully.

Notes

If the failure persists after this change, disk space can be ruled out and we should investigate permissions or archive corruption.

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}