Add support for supplying input zip files next to directories

[miensol]

With this change it is possible to run
allure generate --report-dir ./out ./source-1.zip ./source-2.zip ./source-3

Context

We're building a POC that would bring together tests results from various CI jobs.
We've attempted to run allure from AWS Lambda. Raw tests results are synced from S3 to an EFS attached to Lambda. The performance of generating the report is terrible when compared to local execution. It turned out that the majority of the time the lambda spends on checking files metadata. This is understandable as allure needs to list files and directories.

In order to tackle this, we'd like to zip test results i.e. thousands of files, sync the archives to the EFS attached to the Lambda instead of raw test results.

The way it was implemented was to run readers (except the zip results source plugin) again after opening the zip archive.

Checklist

• Sign Allure CLA
• Provide unit tests

[noomorph]

The feature looks promising! However, I was wondering if it would be possible to add equal support for *.tar and *.tar.gz archives as well.

The motivation behind TAR archives is especially interesting for custom Allure runtime writers. If a writer appends files (like 9283749-result.json and 2384978923-container.json) straight to a tar archive instead of a directory, it can unload the filesystem from operations related to directory/file management, without even having to compress things. I believe this could significantly improve performance, especially on 5000-6000 test suites.

[A1exKH]

Code LGTM.

Please resolve conflicts for this PR.