feat(integration): add action to free space on runner

[sgaist]

Summary

Some integration tests, more specifically those for python, often fail with an out of space error.

This PR adds a new job with an action that frees some space on the runner which allows these tests to pass successfully.

Use Cases

Ensure successful runs of integration tests, more specifically those from the python buildpacks.

See:

paketo-buildpacks/conda-env-update#464
paketo-buildpacks/poetry#555

As example of run failures.

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).

[dmikusa]

I think my biggest concern is taking on a dependency in the form of this 3rd party action that doesn't seem well maintained. There hasn't been a release in a long time and there is at least one PR asking for improvements with no responses.

Not that this is an action that needs constant maintenance, but this gives me cause for concern: jlumbroso/free-disk-space#48

Personally, I'd like to see one of the two things happen:

1. Just copy a couple of the rm -rf's into a step with a run: directly. It's not rocket science and our tooling will push this snippet around to where it needs to go.

2. Copy the implementation from this PR Updates from several community members jlumbroso/free-disk-space#48 into our actions. This has several improvements including using rmz which is a much faster alternative to rm. Then we use our own action.

No strong preference which, as both avoid a dependency on a 3rd party.

[sgaist]

I think that the second option is a good alternative, in case we would need some additional space we will have all the possible cleanup at hands.

[sgaist]

I tested the use of the action in paketo-buildpacks/conda-env-update#464 and looks like it's working correctly.

[dmikusa]

Looks good, one last question. How would one go about setting the env variable to enable this option? The workflow files are managed by this repo, so where would you set that env variable to make it take effect? Would that be in the repo Settings -> Actions? Thanks

[sgaist]

I knew I was missing testing something.

Well, good thing you asked, I was wrong. It's the vars context I should have used.

For the rest, yes, it should be set at the repository level.