Fix filter_policy object leak in NodeStore backends

Just as a style comment, it's better form to immediately put the raw pointer into the smart pointer, and then use it after that.

The reason is that you want to minimize the gap between "creating the pointer" and "making sure it can't be leaked".

In this case, assigning options.filter_policy isn't going to throw an exception so it's academic.