Free disk space before running build_release_candidate

[damccorm]

Right now, we're repeatedly running out of disk space when trying to publish docker images. This should free up ~30 GB for us to use.

https://issues.apache.org/jira/browse/INFRA-24918 requests that infra allow list this action

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @Abacn for label build.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[damccorm]

R: @lostluck

[damccorm]

(the action has now been allowlisted)

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

[lostluck]

I have a small concern that the action might delete things we need to use during the docker build but we may as well merge this in now, and not into the release branch to give me an "out" to the current state, if we need an RC3, when we can verify this.

[damccorm]

I’m pretty confident it won’t do that, it has been used with docker pushes in other contexts. Agreed on the merge and find out strategy though