If the on-page overflow cell is known to be WT_CELL_VALUE_OVFL_RM,
there's no reason to acquire/release the overflow lock, it's not
like the value gets re-instantiated somehow.  Fast path that case;
it's hard to imagine a workload where it makes a difference, but
it's not like it costs us much code, either.