Corrupt Archive handling

[griembauer]

This PR adapts SADASADAM as follows:

• Solves Error in post processing #5: Corrupt .SAFE.zip/.SAFE/.tar.gz scene archives are removed and downloaded again (with up to three tries)
• The download_dir does not have to be defined in the eodag-conf file, it is enough to define it in the SADASADAM config file
• A bug is fixed that only a subset of all found scenes is downloaded. The search function of eodag provides search results by page, thus only downloading the first page, if the results are passed to the download_all-method. This occurs only for downloads of a large number of scenes. The search_all method is used instead

[mmacata]

Thanks for that!

The try block in extract_and_delete_tar_gz_files seems really large, so that no detailed exception can be catched but only a general one. And it might be a bit unintuitive that the return value is corrupt_files. But overall it seems logical and it is clear why, so just take these as hints and feel free to merge :)

[griembauer]

Thanks! I agree to your points - the try block is really large because we don't really know in what ways downloaded files can be corrupted and this way it is made sure they are removed and the code carries on even if an not anticipated error occurs during archive extraction.