Handle incompatible record in Riak 1.4.0.

Return badrpc calls with an incompatible message when unable to
determine which versions of nodes are communicating in a mixed-
version cluster.

Switch to macros for record definitions.

Also, suppress information in the UI when detecting this incompatibility
to prevent from the display of NaN values.
Merge pull request #123 from basho/csm-1.4-bad-record-rebased

Handle incompatible record in Riak 1.4.0.
Roll version 1.4.1
Use new deps
Resolve incorrect capability negotation order.
Use expanded record macro.
Merge pull request #132 from basho/csm-fix-capability-negotation

Resolve incorrect capability negotation order in 1.4.
Merge pull request #133 from basho/csm-fix-partition-badmatch

Use expanded record macro.
Incompatible is less serious.

Ensure that the message regarding incompatible nodes is explicitly
clear and doesn't trigger errors.

This is necessary because even in a pure 1.4.1 cluster, depending on
how nodes are started capability negotation might take a few seconds,
where some nodes will be shown as incompatible.
Merge pull request #135 from basho/csm-clarify-incompatibility-1.4

Incompatible is less serious. (1.4.1)
Add overall status.

Return an overall status that can be used to monitor cluster
transitions.
Merge pull request #137 from basho/csm-introduce-new-status-1.4

Add overall status.
Merge branch '1.4' into csm-merge-1.4

Conflicts:
	priv/admin/js/core.js
	priv/admin/js/generated/templates.js
	rebar.config
	src/riak_control_formatting.erl
	src/riak_control_session.erl
	src/riak_control_wm_cluster.erl
Merge pull request #138 from basho/csm-merge-1.4

Merge 1.4 into master and reconcile changes.