cache each range request

[geospatial-jeff]

• Caches each range request rather than each internal block.
  • This has the upside of caching the file header as well as each block.
  • The downside is the bytes themselves are cached instead of the decompressed array, so repeated calls to the same tile require decompressing multiple times.
• There is still work to be done to ensure we aren't caching the same byte multiple times in situations where a single byte is part of multiple ranges.
  Ref Caching merged range requests #30

[codecov-commenter]

Codecov Report

Merging #41 into master will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #41      +/-   ##
==========================================
+ Coverage   94.94%   94.96%   +0.02%     
==========================================
  Files          10       10              
  Lines         712      715       +3     
==========================================
+ Hits          676      679       +3     
  Misses         36       36              

Impacted Files	Coverage Δ
aiocogeo/cog.py	96.63% <ø> (-0.22%)	⬇️
aiocogeo/config.py	100.00% <100.00%> (ø)
aiocogeo/filesystems.py	92.56% <100.00%> (+0.59%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1043488...7e8a0bc. Read the comment docs.