konsti 5435d44756 Introduce `Cache`, `CacheBucket` and `CacheEntry` (#507) ... This is mostly a mechanical refactor that moves 80% of our code to the same cache abstraction. It introduces cache `Cache`, which abstracts away the path of the cache and the temp dir drop and is passed throughout the codebase. To get a specific cache bucket, you need to requests your `CacheBucket` from `Cache`. `CacheBucket` is the centralizes the names of all cache buckets, moving them away from the string constants spread throughout the crates. Specifically for working with the `CachedClient`, there is a `CacheEntry`. I'm not sure yet if that is a strict improvement over `cache_dir: PathBuf, cache_file: String`, i may have to rotate that later. The interpreter cache moved into `interpreter-v0`. We can use the `CacheBucket` page to document the cache structure in each bucket: 		2023-11-28 17:11:14 +00:00
..
remote_metadata.rs	Introduce `Cache`, `CacheBucket` and `CacheEntry` (#507)	2023-11-28 17:11:14 +00:00