Improve cacheability in Python client builds

[richscott]

The python-client.yml workflow runs the Mage target test2epython, which does a build of the python-client Docker image each time, then runs it. Can the built image be cached?

Tasks:

• using the cached tools (because of the mage target and it's dependencies that need the tools)
• set up image for caching

[pavlovic-ivan]

Looks like this issue will have two parts. One part is using the cached tools (because of the mage target and it's dependencies that need the tools), and the other one is the image. So i suggest either adding two checkboxes to the description, so we can visualise this, and then i will link the PRs that resolve this.

Currently in progress is restoring the cached tools for the jobs in Python client workflow (so, part 1 of my suggestion above). PR for this is in draft on my fork

[richscott]

@pavlovic-ivan Task list with two items added to the description - feel free to adjust/fix the wording.

[pavlovic-ivan]

@richscott thank you!

[pavlovic-ivan]

PR for this issue (task 1): #3244

[pavlovic-ivan]

Hi @richscott. I did investigate the task #2 here. Caching the docker layers will reduce the job by ~1m, but will add additional caches to Github actions, which will hit the 10GB limit at some point. Are you ok with closing this entirely?

FYI: @dave-gantenbein

[richscott]

I agree - marking this as done - great work!

[pavlovic-ivan]

Thanks!