[upload] Added support for tar.gz files

[EvanBacon]

Why

• Expo EAS produces tar.gz files that need to be extracted before they can be uploaded. Because of this expo upload:ios --url <artifact> doesn't work. Likewise expo upload:ios --path </Downloads/artifact> can also be easy to mess up.
• Because the error that gets thrown Failed to upload the standalone app to the app store. Zip end of central directory signature not found is part of Fastlane we can't throw a more useful error in an elegant fashion.
• Legacy code from BaseUploader to the submission service utils. This unifies the logic a bit more.

How

• Check if the file path ends with tar.gz - this is pretty fragile.
• Extract the tar and search its contents for an ipa, apk, or aab file.
• Rename a destination path to have the correct extension and move the app file to that path.
• Continue uploading using the new extracted file.
• Refactored the export command to use tar + got instead of targz + axios - logic is also tested now.

Test Plan

• Wrote unit tests to ensure that the tar extracting works as expecting from remote URLs or local paths.
• Manual testing for iOS:
  • expo upload:ios --path /path/to/eas-output.tar.gz
  • expo upload:ios --url http://128.0.0.1:3000/app.tar.gz
  • expo upload:ios --path /path/to/app.ipa
  • expo upload:ios --path http://128.0.0.1:3000/app.ipa

[dsokal]

I'm requesting changes mostly because of the addition of a new package for uncompressing tar archives. We already have targz installed so we should either use it or refactor Expo CLI to use the new one and remove the old one.

[dsokal]

Also, heads up that this code is a legacy. We already refactored/reimplemented Android uploads so they use Submission Service. The code lives in src/commands/upload/submission-service/. I'm not saying you should move it there (or start implementing iOS uploads with Submission Service) but in my opinion, it's not worth spending too much time on improving the old legacy command that we'll eventually rewrite entirely.

[EvanBacon]

Didn't take too long to implement this and I think it'll end up being valuable since I'm sure people will attempt to use it with EAS (I already did).

[dsokal]

Looks good to me. Please update the changelog!

[LinusU]

@EvanBacon with this change, only one single process can upload one build artefact at a time, since otherwise the file will be deleted from under that process. E.g. trying to run expo upload:ios and expo upload:android in parallel will have one of them fail with either:

Error setting value '/tmp/expo-submission-service/foo-xxxxxx-signed.aab' for option 'aab'
Could not find aab file at path '/tmp/expo-submission-service/foo-xxxxxx-signed.aab'

or:

Failed to upload the standalone app to the app store.
Could not find file at path '/tmp/expo-submission-service/foo-xxxxxx-archive.ipa'

We have build scripts that submits several builds at the same time, and this is currently breaking our workflow. Would it be possible to use a new folder each time, instead of always using expo-submission-service?

I'll send a pull request with that change, but I'm also happy to consider any other approach to solve this 👍