test_cursor02 is failing on tiered tables. Appears to reset to the beginning of the table after removing a record rather than keeping the cursor positioned at the location of the removed record.

SUMMARY:  The problem is that we're using cursor->insert() rather than cursor->update() to insert the tombstone record during remove.  These methods differ in that insert() doesn't leave the cursor positioned, but update() does.  So we need to use the correct one, depending on whether the cursor was positioned before the remove() call.