Increase timeout for reading data from resources to 30 seconds

The introduction of LZMA compression for payloads can mean that when
handling already-compressed attachments, especially those in large
sizes, the default timeout of 10 seconds can be exceeded. This is
particularly evident for machines with rotational disks or full disk
encryption.

This has particularly bad effects on item syncing:

1. The resource retrieves an item, and starts compressing the payload.
2. The compression takes more than 10 seconds, so the resource is
   disconnected from Akonadi due to the timeout.
3. Upon reconnection, there is an attempt to rollback the change, but
   the change did not actually take place, so a bunch of errors
   regarding transactions are logged.
4. The database for that resource and that collection is left in an
   inconsistent state.
5. This can cause the resource to ultimately get stuck on its jobs.

Fixing the actual problem is probably far more convoluted, but a quick
workaround would be to increase the timeout up to 30 seconds, to stay on
the safe side.

This change was tested on a laptop with FDE that could not sync
attachments larger than 5M: after the change, the syncing was performed
sucessfully.
1 job for master in 60 minutes and 6 seconds (queued for 34 minutes and 32 seconds)
Status Job ID Name Coverage
  Build
failed #72984
linux kf5-qt5 qt5.12

01:00:06

1.0%
 
Name Stage Failure
failed
linux kf5-qt5 qt5.12 Build The script exceeded the maximum execution time set for the job
tests/libs/pluginloadertest.cpp               12       0     0%   16,18,20,22-25,28-30,32,35
tests/libs/subscriber.cpp 15 0 0% 14,16-21,23-26,28-31
------------------------------------------------------------------------------
TOTAL 52371 741 1%
------------------------------------------------------------------------------
Uploading artifacts for successful job
Uploading artifacts...
build: found 6392 matching files and directories

ERROR: Job failed: execution took longer than 1h0m0s seconds