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.

I still recommend changing the name of this function to prevent future code like:
````
dbcon.lock();
````
from passing code review.  The following would be more likely to attract deserved attention:
````
dbcon.get_unique_lock();
````
To retain your original functionality, consider overloading this function like so:
````
std::unique_lock<mutex> get_unique_lock()
{
    return std::unique_lock<mutex>(mLock);
}
std::unique_lock<mutex> get_unique_lock(std::defer_lock_t defer)
{
    return std::unique_lock<mutex>(mLock, defer);
}
````
This would be more readable at the caller site:
````
auto lk = dbcon.get_unique_lock(std::defer_lock);
````
as opposed to:
````
auto lk = dbcon.get_unique_lock(false);
````