Dealing with package rot

[springmeyer]

We have packages that either no longer build, accidentally broke due to changes in mason itself, or never should have worked because of buggy script.sh usage.

Going to use this ticket to hang ideas for dealing with this. Currently:

• Look at s3 logs for usage of packages. Delete/cull any that are not in use within last month
• Look for problems and fix the rest so they build.
• System to test that all current packages build (travis won't work for this since our triggered API is rate limited at 10 builds and building everything at once would timeout so we'd need to launch a separate build farm).
• Write Mason v2 that supports each project building and publishing packages to fully dodge this issue of maintaining old versions.