CI: consolidate space freeing steps

### Is your feature request related to a problem or challenge?

We've faced issues with storage space on our CI runners, so we introduced steps to free up space for them across various actions:

https://github.com/apache/datafusion/blob/302dbc8e4b787ed12c16459fca0ce4e32f66ab2e/.github/workflows/extended.yml#L89-L113

https://github.com/apache/datafusion/blob/302dbc8e4b787ed12c16459fca0ce4e32f66ab2e/.github/workflows/rust.yml#L267-L288

https://github.com/apache/datafusion/blob/302dbc8e4b787ed12c16459fca0ce4e32f66ab2e/.github/workflows/rust.yml#L359-L391

### Describe the solution you'd like

We should look into consolidating them together if possible so can apply to all our runners/actions.

Need to consider that some actions are on bare machine runners and others are on containers.

### Describe alternatives you've considered

_No response_

### Additional context

See https://github.com/apache/datafusion/pull/18709

Compare the space-freeing steps in .github/workflows/extended.yml:89-113 and .github/workflows/rust.yml:267-288, :359-391, then review pull request 18709 for context. Determine whether they can be consolidated while supporting both bare-machine runners and container-based actions. Done means the shared approach applies to the relevant runners without breaking those workflow types.

Written by the indexing model from the issue text.