Implement caching based on file sizes and file content where possible

Sometimes we can use etags, Azure provides the md5 hash, some providers have "versions," and there may be other options. Currently trusting file times is a little flaky.

Can we store the etag info on the local file somehow natively? It would be good if this metadata was around to be used across processes, etc.

We aren't doing this now, but we should check file sizes before we even check times. If sizes are different, the files are definitely different. Then we can fallback to if times are different, they are possibly different. Then, hashes can confirm files are different.