[NewTopic] ZipArchive memory usage should be documented

When reading a ZipArchive from a non-seekable stream, the library loads the entire archive into memory before processing individual members. It looks like this is expected behavior - zip files store entry metadata at the end of the archive, and it's necessary to read the metadata before extracting files.

Though valid, this should be noted in the documentation for ZipArchive so people aren't surprised by the significant memory usage.

[mairaw]

@JeremyKuhne, @pjanotti can you comment on this?

[JeremyKuhne]

@ianha What are your thoughts on this?

[iUnknwn]

Any update on this issue? This ended up forcing us to switch from the built in zip library to a third party tar library in our project - having a note in the docs that this is the behavior from the start would be incredibly helpful.