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.

The Key column can suit that purpose just fine. Right now, it's set to 1. Future versions of the table can have other rows with different Key column values. There are ways to do queries to check if certain fields exist in a table, and sqlite-specific ways to check the existing schema. The query "SELECT COUNT(*) FROM <sometable> where <somefield>=<somevalue>;" will always work as long as <sometable> and <somefield> are there. We can use that for versioning if needs arise.