Currently we have decided to clear cursor bounds inside __wt_btcur_reset, this is one of the many cursor reset functions, another option would have been __cursor_reset we should review this logic toward the end of the project to ensure that it is practical for the users.

__wt_btcur_reset does seem like the better choice as it isn't called from other APIs e.g. __cursor_insert however it seems like it may be inconsistent as they call __cursor_reset instead.