Only cuda jobs generate empty cache on build-main and build-main-self-hosted workflows

[youtalk]

Checklist

• I've read the contribution guidelines.
• I've searched other issues and no duplicate issues were found.
• I'm convinced that this is not my fault but a bug.

Description

According to Autoware CI Metrics, it has been confirmed that the no-cuda jobs can build 2 to 5 times faster due to the PR #4865. However the build acceleration is unstable for the cuda jobs.

https://autowarefoundation.github.io/autoware-ci-metrics/

This is because the GitHub Actions cache generated by the cuda jobs is highly likely to be empty.

https://github.com/autowarefoundation/autoware/actions/caches

Expected behavior

Both no-cuda and cuda jobs are consistently more than twice as fast.

Actual behavior

The cuda jobs remain as slow as before.

Steps to reproduce

Run build-main or build-main-self-hosted workflows.

Versions

No response

Possible causes

A similar issue has been posted for buildkit-cache-dance action, which is used to save the --mount=type=cache cache of docker build on GitHub Actions to the GitHub Actions cache.
reproducible-containers/buildkit-cache-dance#33

We would like to take a workaround for the time being.

Additional context

No response