Allowing an implementation of WT_CURSOR::search that doesn't result in a positioned cursor would allow for some optimizations in that case.

We should add a new configuration option to WT_SESSION::open_cursor that causes search operations performed on that cursor to leave the cursor unpositioned on return. The option may be called unpositioned_search, with a default of false to keep the existing behavior.