Rewrite verifyIntegrity() to work with less memory

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Feature request

Which Nextcloud Version are you currently using: (see administration page)
30.0.4

Is your feature request related to a problem? Please describe.
Yes. With < 256 M memory limit, verifyIntegrity() seems to fail silently with the current version.

Describe the solution you'd like
Make verifyIntegrity() less dependent on available memory. Right now, if the downloaded .zip file does not fit within the constraints of memory, it seems to silently fail which really throws off users without too much technical background. There is no mention of the root cause for the termination.

Describe alternatives you've considered
An alternative could be either skipping verification if the archive is too large (and alerting the user) or at least providing a config option to skip this verification.

Additional context
In some environments, it is not easily possible to increase the memory limit. Also, it is really hard to find out the root cause for this strange behaviour without any hint what is going (which is the current state of affairs).

Start by locating verifyIntegrity() and tracing how it handles downloaded ZIP archives and memory-related failures. Determine how the current silent failure occurs and identify the existing tests or update flow that exercise integrity verification. Done means verification works within a 256 MB limit or reports a clear, actionable failure when it cannot.