space efficient storage for a million EDG binaries

Nobody has claimed this yet.

the "million EDG binaries" (30MB zipped, 140MB raw) would compress well with git

transfer size would stay the same, but storage size would be much smaller = no need for amazon S3 server

migrate tarballs to git:

```sh
#!/bin/sh

if [ -d gitrepo ]; then
echo "error: folder exists: gitrepo. to run test again, run: rm -rf gitrepo"
exit 1
fi

mkdir gitrepo

git -C gitrepo init

# https://github.com/rose-compiler/rose/blob/weekly/src/frontend/CxxFrontend/EDG_VERSION
release_list="$(cat < compiling object code with the `-ffunction-sections` and `-fdata-sections` compiler flags. This has the effect that if you 'insert' a function into a translation unit, the insertion does not cause all of the addresses to change across the whole object file.

https://github.com/elfshaker/elfshaker#applicability

Start by reviewing src/frontend/CxxFrontend/EDG_VERSION and the proposed migration script, then inspect how the current EDG tarballs are stored and fetched. Validate the repository history and tags against the listed releases, confirm Git compression reaches the reported size, and verify that the GitHub archive URL provides the required tarballs without the Amazon S3 server.

Written by the indexing model from the issue text.