feat(ci): disable Docker build cache mode=max option due to disk space problem

[youtalk]

Description

• fix(ci): fix Docker image organization #5002
• feat(ci,docker): disable var-lib-apt cache #5004

Unfortunately, even with the above two corrections, it was found that the cuda job still fails due to disk space issues.

https://github.com/autowarefoundation/autoware/actions/runs/9981995778/job/27586843983#step:5:18544

#145 114.8 fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "mkdir: cannot create directory ‘/root/.ansible/tmp/ansible-tmp-1721262994.3001075-4771-138480599394249’: No space left on device\n", "unreachable": true}

Therefore, this PR temporarily removes the mode=max option from the cache-to setting of docker-build-and-push workflows to reduce the amount of cache export.

Ref. https://docs.docker.com/build/cache/backends/#cache-mode

Tests performed

https://github.com/autowarefoundation/autoware/actions/runs/9983663011

Effects on system behavior

Not applicable.

Interface changes

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

[oguzkaganozt]

Switching to a different build farm other than default github runners might be better workaround to get the most out of the docker caching. @mitsudome-r

[xmfcx]

Switching to a different build farm other than default github runners might be better workaround to get the most out of the docker caching. @mitsudome-r

@oguzkaganozt GitHub public runner are an invaluable resource for us, they provide us with 20 machines with 4vCPU with reasonable specs.

I realized that we had the artifacts within the images just today. Autoware CI doesn't even make use of them. Once we remove them from the current image and split them into something else, space won't be an issue for a long time.

See:

• Lightweight devel build for docker #4991 (comment)
  with the half the image size.