MID-6955: S3 actions using s5cmd

[dkaruga-piwikpro]

Previous attempt

We had already implemented s5cmd in PRs (#169, #170), but it was unstable because of too many workers sending requests at once.
It was reverted in #172 and #173.

Current attempt

We are still using fast s5cmd but I researched and tweaked the configuration. It should work as fast as before, but more stable than before.
Changes compared to the previous attempt:

• --numworkers 50 previously we were using the default value of 256. It was as fast as 50, but very resource-intensive for the internal network and our proxy for S3.
• --retry-count 30 previously we were using the default value of 10. It's just a safety measure in case we still have some issues with the network.

Tests

I checked this branch using tag-tests.
If you want to check it before merging, you need to use branch MID-6955-s3-actions-using-s5cmd-test.

Why is this a separate action?

This is a separate action rather than replacing our existing workflow because previous implementation was unstable.
We need to verify that this current implementation does not have any issues before making it the default.

[mateusz-uzarowicz]

I tested the new solution on PIT. The sample test size was small, but we still get the Allure report very quickly - even faster when using the AWS CLI.
The Tag tests will be the decisive factor, since there are many of them, but it looks promising (1m < 5m 🎉).
I’d also prefer to wait for results from other where report generation currently takes longer than the tests themselves