Promise files for caching not reliably deleted

🐛 Describe the bug

With version 0.5.0 the promise files for caching are no longer reliably deleted. Instead of trying to delete the file as soon as the cache has been created torchdata seems to wait for the end of the data pipe before it tries to delete it. I did not encounter this issue with version 0.4.1

Versions

PyTorch version: 1.13.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 13.1 (arm64)
GCC version: Could not collect
Clang version: 15.0.4
CMake version: version 3.24.3
Libc version: N/A

Python version: 3.10.8 (main, Oct 13 2022, 09:48:40) [Clang 14.0.0 (clang-1400.0.29.102)] (64-bit runtime)
Python platform: macOS-13.1-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.4
[pip3] pytorch-lightning==1.8.1
[pip3] torch==1.13.0
[pip3] torchdata==0.5.0
[pip3] torchdistx==0.2.0+cpu
[pip3] torchmetrics==0.10.2
[pip3] torchtext==0.14.0
[pip3] torchvision==0.14.0

No files, tests, or entry points are named. Start by reproducing the caching behavior with torchdata 0.5.0 and 0.4.1 on the reported platform, then trace the promise-file lifecycle in the caching implementation. Done means promise files are deleted promptly after cache creation without breaking data-pipe completion.