BUG: Close file handle with lock=False

[snowman2]

• Tests added
• Fully documented, including docs/history.rst for all changes and docs/rioxarray.rst for new API

For the caching file manager, it closes the file handle from the cache ref. Since there is no cache to close with, I am thinking that the class should keep track of it like the DummyFileManager ref. (ping @TomAugspurger in case you have thoughts on this).

[TomAugspurger]

I haven't looked closely at the issue / PR, but just want to note that you may want to be careful to only close the file handle when rioxarray is the one that created it. If you're passed an open file handle then typically the user should be the one to close it. Though like I said, I haven't looked closely so I don't know if that applies here.

[snowman2]

Thanks for your comment @TomAugspurger 👍

you may want to be careful to only close the file handle when rioxarray is the one that created it. If you're passed an open file handle then typically the user should be the one to close it.

This only changes the URIManager used in rioxarray.open_rasterio. If I understand what you are saying, I think this should be safe. Additionally, this PR makes the close method functional as previously it just has pass in there.