<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=379219) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=379219) </details> <!--IssueSummary end--> As discussed in POC https://gitlab.com/gitlab-org/gitlab/-/issues/376261 GitLab Migration should start supporting relations import compressed with zip. ### Proposed solution 1. Update `BulkImports::FileDownloadService` to be able to download `relation.zip` along side with `relation.tar.gz` 2. Update `BulkImports::FileDecompressionService` to be able to decompress `.zip` files along side with `.tar.gz` depending on type of the compression used (by updating the class itself or using composition/inheritence to achieve this) 3. Since in case of `.zip` there is no Tar involved, we should update the codebase to not do any systemcalls to `tar` when decompressing data with `zip` 4. Make sure all pipelines import data same as before 5. Put changes behind a short lived feature flag. Since we're going to be supporting both types of files for some time it makes sense to have the feature flag for testing purposes until we iron out any found issues