Fix unknown types caused by typos
Match some expected return values that are important

Some of these should really cause crashes when errors are returned,
since later expressions expect them to have succeeded.
RIP Legacy gossip

Removed the related dead code.
Background manager types were incorrectly specified
Split resolve/2 into to two functions which have disjoint signatures.
Fix some type warnings related to timers
Correct the type of human_time/3, was too narrow
Remove overly verbose annotations that can be inferrred
Remove case clauses in riak_core_security that will never match
orddict:orddict/0, not orddict:orddict/2
Simplify the return type of maybe_ensure_vnodes_started/1 so callers don't have to match.
Comment out this unused expression.

TODO: Ask @jonmeredith @jtuple what this was for
equal_cstate/3 is never called with true (except in tests) and not exported.

The case where it returns verbose information is only useful for the
test, and should probably instead be tested with EQC.
Fix two obscure unmatched returns.
Correct case for missing clause related to ring resizing.

TODO: This seems like a real bug that should be addressed. Ask @jrwest
Remove commented code.
Unify the type of case expression so we need not match it.
Remove more legacy gossip warnings
Match the return value of rpc_every_member.
The function() type refers to funs, not function names.