This commit fixes an edge case in which the config filename is never
declared if the config is set but the file does not exist on disk.

Created projects default to private, we need to set the visibility in
the script to make them public.

This fixes a bug where, if there were no errors in uploading binaries,
failure is referenced before it was ever declared.

This fixes an issue that occurred while running the new gitlab script on
the gettor machine. Newer library versions require the b64 encoded byte
string to be converted to ascii text.

This commit cleans up the script a bit by:
- making more detailed comments,
- streamlining the choice of remote repository
- printing all output to std error
- captilization consistency

We now have a separate script for both GitLab and Github endpoints.

Updated and refactored the script to upload tor browser binaries to the
gitlab remote using the GitLab REST API.

Add tests to check sent email messages.

This fixes a bug where we exceed our google drive quota. Deleted files
were moved to a trash bin and not removed from storage entirely.

This modifies update_files to update each tor browser binary in gitlab,
internet archive, and google docs, and then delete the binary before
downloading the next one. This will save storage space on the gettor
host.

Breakdown strings for translations
Delete unused scripts

This script had important commands for updating internet archine and
google docs. The github release script has been renamed to
update_github.

Have the script read directly from an environment variable instead of
passing the token in as a command line argument. This will hide it from
other processes.

Also removed downloaded files to prevent a messy directory.

- also fixed a bug where releases won't be deleted untless the assets
are removed first

The script will continue with the rest of the uploads but will exit with
a non-zero code so that we'll be notified to upload the missing files
manually.

We were running out of space in both of our github and gitlab
repositories due to storage limits. This change switches to using the
github REST API to upload torbrowser binaries as releases. Releases are
not subject to the space limits of repositories and, even better, do not
count against our bandwidth limits when users download them.