v2.4.0: updated search

Write queues are now checked as opposed to causing a key to be ignored. This means, if a key is in the queue and a read is attempted, instead of waiting and retrying, the value will be read from the queue to quickly get the most current version of the key. This also applies for searches, when searching the database, after checking the written database, the search will check the queue, if for some reason the updated version contains a queued write that makes a key no longer accurate to the query, the key will be removed as it's most recent version does not apply. If there is a key in the queue that was not in the database that the query applies to, it will be added to the result. This is a pre-release because further testing should be done.