ZipPackageFolder: releaseUpwardRef only calls clearParent, remove it.

Since commit 0c5bb3f42d38b3c16015dc0a45defd1b1dad4f92.

Change-Id: I5511f9dc829aca42790f05cb8fb3ebd83b2acad4
package: Move most ZipOutputEntry's methods back to ZipOutputStream

We want to use ZipOutputEntry only for deflating (and maybe rename it).
ca13a9377e4a36436e4c82bb33648d0f3b6db6f5 was not a good idea because the
data still needs to be written sequentially anyway. Otherwise it's hard
to get offset positions of individual entries right.

Since this commit rawCloseEntry needs to be called always; also when we
use write&closeEntry because we don't call writeEXT in closeEntry
anymore.
Need to rename and add comments later.

Change-Id: I03bd48ca6e108e6253a77a137746165909ca3c3d
package: Zipping STORED entry is the same as rawWrite and we don't encrypt it

Change-Id: Ie3f8ac261a70c9a2b5182fc7d36938d0a46ec045
ZipOutputEntry: m_pCurrentEntry is always set

Change-Id: Ib6a69a83f4a378df838b2231b9eba7fba49cd9f1
package: Use memory stream for compressing zip entries

Change-Id: Ibf81dc3cd8a9a9da3dfd6ee6e587a522c4d56a44
There is no XZipOutputEntry interface

Change-Id: Ib8fa3351ba25416a13d6c8bf63bd5fc8e43703c5
package: Do not use hacky bit 1<<4 in ZipEntry::nFlag

Change-Id: I504f5c0c9aa9b655ffb53d9820a33677dad6aa08
package: Call writeLOC always after putNextEntry explicitly

Preparation step to parallel deflating.
Rename putNextEntry to setEntry and make it a static function.
We need to call setEntry before starting thread but writeLOC after.

Change-Id: I99a9ffa7dc4c18b47c621847b48bf8469bfb789a
package: Finally implement parallel zip entries deflating

For that:
1, create ZipPackageStream::successfullyWritten to be called after
the content is written
2, Do not take mutex when reading from WrapStreamForShare - threads should
be using different streams anyway, but there is only one common mutex. :-/

Change-Id: I90303e49206b19454dd4141e24cc8be29c433045
HACK to avoid expensive and pointless deflating of jpeg files

This is not intended to land in master; it's just for testing.

Change-Id: If93cb78dcef903584de7b23f37282852c6d69f35
package: Add possibility to disable deflating in a thread

Change-Id: I4d98b6f8b3315b731206700eb65f08463299dda3
Disable deflating in a thread

Change-Id: I1803cd61e283bcc20d4d59870121e785bc778f4a
Revert "HACK to avoid expensive and pointless deflating of jpeg files"

This reverts commit 8c10cb5edc6902a96dc265d36faad0a8382b1a4a.
Simplify input parameters to just take the sequence

Change-Id: Ic2538ca8b0f7261064e1dfbf3884dd452003c797
ZipPackageStream::getRawData can be private

Change-Id: I66cbbfb2aa6abc6c8ebe34d9ea69855436c23edd
package: Increase size of buffers

I just want to see what's going to happen - if anything.

Change-Id: Iba09c261126654ab19fc5755b3923b406db15031
Test parallelism again.

Change-Id: I495e147b679b770c479eb0bb2c2714d815e5b9e9
package: Do not deflate small streams in a thread

Change-Id: Iae804a34f344aa793a6d5c13315f7bc1eb64c0a2