🎨 Frees up space on runner for [build] docker images part of the CI

[GitHK]

What do these changes do?

We are constantly running out of disk space when building the docker images.
To avoid manually clearing the GitHub caches this is a solution that will work.

Removing some unused space for the [build] docker images stage will help finishing the builds.

NOTE the space gained is based on the assigned runner that's why sometimes the CI goes though. In my two attempts I managed to get 14G extra free space. For more details see explanation here:

• WARNING: Github runner disk layout is now a fast moving target, breaking this action for many easimon/maximize-build-space#48
• https://github.com/easimon/maximize-build-space

Gains

Available storage before:
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        73G   53G   21G  72% /
tmpfs           7.9G  172K  7.9G   1% /dev/shm
tmpfs           3.2G  1.1M  3.2G   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sda15      105M  6.1M   99M   6% /boot/efi
/dev/sdb1        74G  4.1G   66G   6% /mnt
tmpfs           1.6G   12K  1.6G   1% /run/user/1001
Available storage after:
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        73G   38G   35G  53% /
tmpfs           7.9G  172K  7.9G   1% /dev/shm
tmpfs           3.2G  1.1M  3.2G   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sda15      105M  6.1M   99M   6% /boot/efi
/dev/sdb1        74G  4.1G   66G   6% /mnt
tmpfs           1.6G   12K  1.6G   1% /run/user/1001

Related issue/s

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.8%. Comparing base (cafbf96) to head (e829d1f).
Report is 602 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #6475      +/-   ##
=========================================
+ Coverage    84.5%   97.8%   +13.2%     
=========================================
  Files          10      13       +3     
  Lines         214     324     +110     
  Branches       25       0      -25     
=========================================
+ Hits          181     317     +136     
+ Misses         23       7      -16     
+ Partials       10       0      -10     

Flag	Coverage Δ
unittests	97.8% <ø> (+13.2%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 23 files with indirect coverage changes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[pcrespov]

Let's try but it looks to me a bit Q+D solution
BTW, how did you test the space drop in the build container. Note that I was cleaning the cache...

[YuryHrytsuk]

I agree with @pcrespov. This looks more like a hack than a solution. Also according to the author itself (easimon/maximize-build-space#48).

If you think it is fine, go ahead