Fix incorrect address in connectivity check report:
The remoteAddress is the address as seen on the socket, which for
incoming connections has a random port chosen by the remote implementation
that is different from the port number used to accept connections by the
remote listening socket. The checkedAddress is the remote address as seen
on the socket, combined with the port advertised in the TMEndpoints message.
This fixes the reporting and metadata associated with addresses tested
for connectivity.

The README has been updated to reflect that uptime is no longer part of
the metadata associated with IP addresses saved for bootstrapping.
Cleanup: Combine Section and BasicConfig, move to basics
Remove unused file
[checkpoint] Testing out the functionality of the ws.
[checkpoint] Use new wallet class in ripple-lib
* Pending pull https://github.com/ripple/ripple-lib/pull/161
[checkpoint] Submit and process a transaction
[checkpoint] Simulate random transactions over time
[checkpoint] Ledger summary stats.
[checkpoint] Don't output the full ledger.
[checkpoint] Need a newer version of ripple-lib
* Force exit on server disconnect.
[checkpoint] Organize a function library. Attack scenario.
[checkpoint] Create a bunch of trustlines for 1 account.
[checkpoint] Up the ledger_accept timeout
[checkpoint] more timing tweaks
[checkpoint] use the function library in test4.
[wip] Transaction rate measuring.
[wip] more logging
[wip] Date stamps on log messages. Smaller funding amount.
[wip] separate ledger watcher to collect stats
* Pregenerate wallets. This will allow the secret keys to be known between runs.
[wip] int -> var. Keep track of event indexes.