Cache upload does not handle 429 error

Describe the bug
Occasionally, caching actions fail at Post step:

Post job cleanup.
/usr/bin/tar --posix --use-compress-program zstdmt -cf cache.tzst --exclude cache.tzst -P -C /runner/_work/beam/beam --files-from manifest.txt
Warning: Failed to save: Cache service responded with 429 during upload chunk.
/runner/_work/_actions/actions/setup-java/v3.8.0/dist/cleanup/index.js:401
                        throw new Error(`Cache upload failed because file read failed with ${error.message}`);
                        ^

Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
    at ReadStream.<anonymous> (/runner/_work/_actions/actions/setup-java/v3.8.0/dist/cleanup/index.js:401:31)
    at ReadStream.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at errorOrDestroy (node:internal/streams/destroy:220:7)
    at node:internal/fs/streams:262:9
    at FSReqCallback.wrapper [as oncomplete] (node:fs:671:5)

Example run: https://github.com/apache/beam/actions/runs/6307333506/job/17123805683?pr=28079

A solution could be ignore this transient error similar to here: https://github.com/coursier/cache-action/issues/131

Additional context
original issue: https://github.com/actions/setup-java/issues/543

Start with the failing Apache Beam workflow and the referenced setup-java cleanup/index.js stack trace, then compare the cache-upload behavior with the linked coursier and setup-java issues. Identify where a 429 during chunk upload is surfaced during post-job cleanup; done means the transient response no longer causes this cleanup failure while the behavior for other upload errors remains clear.