New ResourceManager for managing server load.

* Track abusive endpoints
* Gossip across cluster.
* Use resource manager's gossip support to share load reporting across a cluster
* Swtich from legacy fees to new Resource::Charge fees.
* Connect RPC to the new resource manager.
* Set load levels where needed in RPC/websocket commands.
* Disconnect abusive peer endpoints.
* Don't start conversations with abusive peer endpoints.
* Move Resource::Consumer to InfoSub and remove LoadSource
* Remove port from inbound Consumer keys
* Add details in getJson
* Fix doAccountCurrencies for the new resource manager.

src/ripple_data/protocol/ripple.proto

@@ -90,10 +90,19 @@ message TMClusterNode
     optional string          address         = 5;
 }
 
+// Sources that are placing load on the server
+message TMLoadSource
+{
+    required string          name            = 1;
+    required uint32          cost            = 2;
+    optional uint32          count           = 3; // number of connections
+}
+
 // The status of all nodes in the cluster
 message TMCluster
 {
     repeated TMClusterNode   clusterNodes    = 1;
+    repeated TMLoadSource    loadSources     = 2;
 }