SHAMapStore with online delete

@JoelKatz @nbougalis 

Here's a more detailed description of this effort:

    SHAMapStore: Online Delete
    Makes rippled configurable to support deletion of all data in its key-value
    store (nodestore) and ledger and transaction SQLite databases based on
    validated ledger sequence number. All records from a specified ledger
    and forward shall remain available in the key-value store and SQLite, and
    all data prior to that specific ledger may be deleted.
    
    Additionally, the administrator may require that an RPC command be
    executed to enable deletion. This is to align data deletion with local
    policy.

In general, yes to Journal but there's some rumble going on at startup where the partitions are not fully configured and we have to use `std:cerr` (I'm not saying this is one of those cases). For example, what if we can't find the config file? That has to be reported to `std::cerr` (we need the config file to open debug.log).