Circle CI Caching

1. Cache adaptors(Salesforce is the default)-LP/install
2. Cache the libraries installed with `npm/yarn`
3. Tools that are not explicitly required for your project are best stored on the Docker image.
4. Jobs in one workflow can share caches. Note that this makes it possible to create race conditions in caching across different jobs in workflows.
5. You could make this workflow deterministic by changing the job dependencies: make Job1 and Job2 write to different caches and Job3 loads from only one, or ensure there can be only one ordering: Job1 -> Job2 ->Job3.
6. CircleCI restores caches in the order of keys listed in the restore_cache step. Each cache key is namespaced to the project, and retrieval is prefix-matched. The cache will be restored from the first matching key. If there are multiple matches, the most recently generated cache will be used.
7. When it comes time to restore the cache, CircleCI first validates the cache based on the first (and most specific) key, and then steps through the other keys looking for any other cache-key changes.
8. Caches created via the save_cache step are stored for up to 15 days.