Update rename_node to also set claimant field.

If reip is being used to restore a dead cluster and the previous
claimant node is renamed first then the ring never converges (see below).
This change modifies rename_node to also check the claimant field
and update as necessary.  The ring manager / claimant could also
be hardened to verify the claimant is a valid node in the cluster,
but I suspect that will be worked with riak_ensemble in the near future.

Example with previous claimant dev1 renamed to dev4

red:dev john$ dev1/bin/riak-admin ring-status
================================== Claimant ===================================
Claimant:  'dev1@127.0.0.1'
Status:    down
Ring Ready: unknown

============================== Ownership Handoff ==============================
No pending changes.

============================== Unreachable Nodes ==============================
The following nodes are unreachable: ['dev1@127.0.0.1','dev2@127.0.0.1',
                                      'dev3@127.0.0.1']

WARNING: The cluster state will not converge until all nodes
are up. Once the above nodes come back online, convergence
will continue. If the outages are long-term or permanent, you
can either mark the nodes as down (riak-admin down NODE) or
forcibly remove the nodes from the cluster (riak-admin
force-remove NODE) to allow the remaining nodes to settle.
red:dev john$ dev1/bin/riak-admin down dev3@127.0.0.1
Failed: "dev3@127.0.0.1" is not a member of the cluster.
Convert members and seen in rename_node from list to orddict, fixing broken orddict:find calls after a reip
Merge pull request #603 from basho/bugfix/reip-update-claimant

Bugfix/reip update claimant

Reviewed-by: reiddraper
call Mod:handle_overload_info/2 for unknown msgs in vnode_proxy during overload
Stub out fakemod:handle_overload_info/2 for test

In riak_core_vnode_proxy:overload_test_/0 we use fakemod as a vnode
module because we don't expect any callbacks from the proxy, even in
overload. This prior commit however, ensures that the vnode will get
called back with any messages that aren't handled directly via the
proxy. Previously those messages were dropped on the floor.
Merge pull request #605 from basho/bugfix/handle-sc-vnode-overload

call Mod:handle_overload_info/2 for unknown msgs in vnode_proxy during o...

Reviewed-by: kellymclaughlin
Silence output from core_vnode_eqc and log to file instead
Merge pull request #606 from basho/feature/silence-core-vnode-eqc

Silence output from core_vnode_eqc and log to file instead

Reviewed-by: seancribbs
Use a proxy process when joining/removing SC nodes

Centralize the proxy process implementation in riak_core_util and
utilize that in riak_core_claimant:bootsrap_members/1.

We use a proxy process for riak_ensemble_manager:{join/remove} to handle
any errors resulting from the riak_ensemble_manager crashing, and
to prevent late responses from getting sent to the claimant in the case
that it already got a timeout for the given operation.

Also update dialyzer.ignore-warnings.
Demonitor on success in proxy_spawn/1

When we spawn a proxy process to run a function and if it successfully
returns we need to demonitor it so that we don't receive errant 'DOWN'
messages.
add riak_core_util:proxy_spawn_test/1
Update tools.mk to v0.5.4

Removes the need to specify line numbers in the dialyzer ignore file.
Merge pull request #611 from basho/feature/tools.mk-0.5.4

Update tools.mk to v0.5.4

Reviewed-by: seancribbs
Update tools.mk to v0.5.5
Merge pull request #609 from basho/bugfix/use-proxy-to-prevent-crash-when-joining-sc-nodes-mixed-clusters

Use a proxy process in claimant when joining/removing SC nodes

Reviewed-by: lordnull
Merge pull request #612 from basho/feature/tools.mk-0.5.5

Update tools.mk to v0.5.5

Reviewed-by: russelldb
added exometer & riak_exoport deps
integrated exometer
further exometer fixes
find_entries() new return value