feat(ci,docker): disable var-lib-apt cache

[youtalk]

Description

• fix(ci): fix Docker image organization #5002

This PR fixes the issue #5002 (comment).

Oh, it was failed due to another reason... From my several months experience, docker/bake-action, which is used in docker-build-and-push workflow, tends to cause more problems than docker/build-push-action, which is used in health-check workflow. I will invalidate the relevant cache.

https://github.com/autowarefoundation/autoware/actions/runs/9974064666/job/27560776559#step:5:10093

105.1 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to lock apt for exclusive operation: Failed to lock directory /var/lib/apt/lists/: E:Could not open lock file /var/lib/apt/lists/lock - open (2: No such file or directory)"}

In the case of mount=type=cache,sharing=locked, it should be exclusive even if built in parallel. However, it seems that when using docker/bake-action, the exclusive process occasionally fails.

https://github.com/moby/buildkit/blob/master/frontend/dockerfile/docs/reference.md?utm_source=pocket_reader#run---mounttypecache

Tests performed

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

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.

[xmfcx]

cuda version is failing.

• https://github.com/autowarefoundation/autoware/actions/runs/9981995778/job/27586843983

It also failed for another PR (only for cuda, and early, not related to space issues):

• feat(autoware.repos): remove autoware_auto_msgs #5011
  • https://github.com/autowarefoundation/autoware/actions/runs/9993281928/job/27620306676?pr=5011

[youtalk]

@xmfcx This PR is not a PR to reduce disk space. By merging the subsequent PR #5009, I've confirmed that the health-check and docker-build-and-push were success.

[xmfcx]

I'm merging this bypassing health-check / docker-build (cuda) (pull_request) requirement, hopefully it will be fixed soon.