Automate the deletion of old Gems from servers

[lin-d-hop]

Description

@dacook has recently discovered that old and unused gems on servers just hang there, stagnant, waiting to crash the entire server as memory fills. They are a potential silent killer and you know how we feel about silent killers?
We get to them when they actually break everything, just like everything else we do.

For example, on DE there was about 9gb of unused old gems (over 20% of the disk!).

Acceptance Criteria & Tests

1. Add to the deployment/provision scripts an automated task to remove all old and unused gems. I'm not actually clear about how we'll do this so perhaps @dacook can add some more details.

[dacook]

Thanks Lynne, I propose we remove all unused gems (including older versions) as part of each deploy. It turns out there's already a simple command for that (bundle clean).

If we do it before installing new gems, the previous version of any newly-upgraded gems will remain on the server until the next deploy, which will be helpful in the event of a rollback (although I'm not sure we've ever done that).

If any gem is removed that is later needed again, it can simply be re-downloaded.

I think it will be a very simple change, but will fight the temptation to do it right now..

[dacook]

To consider: staging servers can have several PRs checked out in one day, with different version bumps. This means that gems could get deleted, then need to download again, slowing down deployments.
I don't think that will be a problem most of the time, but when testing large changes like a Rails upgrade, it would be noticeable.

So an alternative to consider would be to clean up based on a time schedule. Eg a cron job to run weekly (or even monthly would be fine).

Whatever we choose, it should be minimum of risk. The goal here is simply to avoid having to randomly clean up old gems on a server every few years..