Restoring calls NewAR -> Restore -> Run

NewAR now calls NewTR
AR.Restore calls TR.Restore
AR.Run calls TR.Run

Implement lifecycle hooks on the task runner

Hook renames

Template hook

Basic Vault hook 

All of this just to get something faster than md5... yeesh.

splits apart local and remote persistence

removes some locking *for now*

All hooks only need to be run once.
Since only one hook can fail per run there's no need to
track errors on a per hook basis.

I think I like this pattern better as some Config vals are mutable
(Alloc) and some aren't and some are used to derive other values and
never used directly.

Promoting them onto the TR struct is a little more work but is hopefully
more clear as to how each value is used.

Tons left to do and lots of churn:
1. No state saving
2. No shutdown or gc
3. Removed AR factory *for now*
4. Made all "Config" structs local to the package they configure
5. Added allocID to GC to avoid a lookup

Really hating how many things use *structs.Allocation. It's not bad
without state saving, but if AllocRunner starts updating its copy things
get racy fast.

UI: Refactor breadcrumbs

UI: Codify common mirage scenarios and make it easy to switch between