Stub out the Transfer analysis

This is a new analysis to complement the escape analysis
Add a .ghci file with some helpers for exploring generated reports
Flesh out the Transfer analysis

Right now it identifies basic owned fields.  It doesn't yet
identify things stored into those fields or deal with the
shape analysis to work with things stored in containers.
Add a tag for reporting Transferred parameters
Add logic to identify rudimentary transfers

Still needs to perform interprocedural propagation, not to mention the
shape analysis steps.
Have the indirect call resolver also resolve direct calls

This can reduce code duplication in some analyses by letting the
interprocedural (call) case handle both direct and indirect calls
uniformly.  If separate handling is required, that is still possible
and no analyses should be negatively affected by this change unless
they expected direct calls to *not* be resolved.
WIP stub out interprocedural part of the transfer analysis
Revise the dependency summary handling
Update the transfer analysis to use the new dependency lookup
Remove an error call since it wasn't really correct
Refactor the summary lookup functions

Warnings about missing dependencies are now generated at this lower
level instead of each analysis being required to deal with it.  There
are now variants of the lookup functions that let clients treat a
missing summary the same way they treat a summary with no annotations.
Update to the sbv-2.9 API (adds a timeout to isSatisfiable)
Depend on newer sbv (2.9)
Update to work with hashable-1.2
Do not use lookupDefault to report errors
Finish the interprocedural transfer pieces.

Still need to handle the shape analysis cases, but this should be
enough to assemble a basic test suite and handle many common cases.
Fix handling of direct calls in the call resolver
Start a test suite for the transfer analysis
Refactor the owned field analysis

The old implementation was incomplete (it could miss some finalized
fields if more than one was finalized by a particular callee).  The
new one is more correct and also simpler.
Add a few more test cases for the transfer analysis