Unify caches

[matthiasdiener]

Questions for the review:

• Is the scope and purpose of the PR clear?
  • The PR should have a description.
  • The PR should have a guide if needed (e.g., an ordering).
• Is every top-level method and class documented? Are things that should be documented actually so?
• Is the interface understandable? (I.e. can someone figure out what stuff does?) Is it well-defined?
• Does the implementation do what the docstring claims?
• Is everything that is implemented covered by tests?
• Do you see any immediate risks or performance disadvantages with the design? Example: what do interface normals attach to?

[matthiasdiener]

This sometimes fails with (via @MTCam):

  File "/p/gpfs1/mtcampbe/CEESD/AutomatedTesting/MIRGE-Timing/timing/emirge/loopy/loopy/schedule/__init__.py", line 2427, in get_one_linearized_kernel
    schedule_cache.store_if_not_present(sched_cache_key, result)
  File "/p/gpfs1/mtcampbe/CEESD/AutomatedTesting/MIRGE-Timing/timing/emirge/miniforge3/envs/nozzle.lazy.timing.env/lib/python3.11/site-packages/pytools/persistent_dict.py", line 568, in store_if_not_present
    self.store(key, value, _skip_if_present=True, _stacklevel=1 + _stacklevel)
  File "/p/gpfs1/mtcampbe/CEESD/AutomatedTesting/MIRGE-Timing/timing/emirge/miniforge3/envs/nozzle.lazy.timing.env/lib/python3.11/site-packages/pytools/persistent_dict.py", line 725, in store
    LockManager(cleanup_m, self._lock_file(hexdigest_key),
  File "/p/gpfs1/mtcampbe/CEESD/AutomatedTesting/MIRGE-Timing/timing/emirge/miniforge3/envs/nozzle.lazy.timing.env/lib/python3.11/site-packages/pytools/persistent_dict.py", line 150, in __init__
    raise RuntimeError("waited more than one minute "
RuntimeError: waited more than one minute on the lock file '/p/gpfs1/mtcampbe/CEESD/AutomatedTesting/MIRGE-Timing/timing/timing-run-caches/xdg-cache/pytools/pdict-v4-loopy-schedule-cache-v4-2024.1-islpy2023.2.5-cgen2020.1-cc795034cc40d49deed34705ca594c96f407a70f-v1-py3.11.8.final.0/ce4930838a82de39199da84f1d4aff9b216cfa3993e844defbaec7a6563dedae.lock' -- something is wrong

[matthiasdiener]

Nightly tests on Lassen seem to run fine with this PR.