Optimize forestdb array index if both new and old key are nil

Update the scenario - If a field value changed from "existing" to "missing" (ie, key = nil), we need to remove back index entry corresponding to the previous "existing" value - to only when new key == nil and oldkey != nil in forestdb slice writer.