Until we can dynamically update the Graph when scrolled into view

Reworks all usages to use configuration.get

Improves best remote caching

In V8 ints less than 2^30 (on 32bit systems) have optimized storage

Renames storage keys for clarity

First pass at converting "blame" commits into a unified model

Reorganizes local git support to exclude from web
Swaps sha1 usages to md5 to avoid needing sha1 on the web (md5 is required by Gravatar)
Avoids crypto-browserfy and imports md5.js directly
Uses platform crypto for random nonce strings

Avoids process.hrtime for web builds

Splits path functions into system/paths module

Moves avatar cache to global storage
Improves avatar cache updates/resets
Improves contributor avatar fetch update

Giving up on better else/catch/finally formatting -- can't fight anymore
Switching to tabs for better accessibility
https://twitter.com/sh4na/status/1146837957200027648

Partial fix for #281- covers the `*@users.noreply.github.com` case.

The `users.noreply.github.com` domain comes from users
making use GitHub's 'email privacy' feature.
Since the noreply address doesn't accept email, a user can't link
their preferred Gravatar to this type of email address.

The upside is that this address is easily parsable into:
* (optional) Github User ID
* Github User Name

We can use either to create the associated avatar link
without actually having to do an additonal request
against Github's user search API.