InnoDB: Failing assertion: pcur->restore_position(BTR_MODIFY_TREE, mtr) == btr_pcur_t::SAME_ALL

Recently upgraded our DB replica server from MariaDB 10.4.22 to 10.6.12. Upgraded a few other prior with no issues. Ran into an assertion error that crashed only on one of our replicas (oddly enough, the others were fine). Stack trace shows an UPDATE statement caused the crash.

```0x40003629b8f0 InnoDB: Assertion failure in file /local/p4clients/pkgbuild-_nuWH/workspace/src/RDSMariaDB/storage/innobase/row/row0upd.cc line 2413
InnoDB: Failing assertion: pcur->restore_position(BTR_MODIFY_TREE, mtr) == btr_pcur_t::SAME_ALL
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mariadbd startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
230302 17:28:39 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.6.12-MariaDB-log source revision:
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=719
max_threads=12002
thread_count=753
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 27964704 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x4060c3208d18
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x40003629b060 thread_stack 0x40000
/rdsdbbin/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xaaaae119ad18]
/rdsdbbin/mysql/bin/mysqld(handle_fatal_signal+0x490)[0xaaaae0a54f40]
linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0x4000243d4860]
/lib64/libc.so.6(gsignal+0xb0)[0x4000245ff530]
/lib64/libc.so.6(abort+0x154)[0x400024600d74]
/rdsdbbin/mysql/bin/mysqld(+0x784864)[0xaaaae0784864]
/rdsdbbin/mysql/bin/mysqld(+0xff0bc4)[0xaaaae0ff0bc4]
/rdsdbbin/mysql/bin/mysqld(+0xff3f80)[0xaaaae0ff3f80]
/rdsdbbin/mysql/bin/mysqld(+0xff50dc)[0xaaaae0ff50dc]
/rdsdbbin/mysql/bin/mysqld(+0xfd4614)[0xaaaae0fd4614]
/rdsdbbin/mysql/bin/mysqld(+0xf2b478)[0xaaaae0f2b478]
/rdsdbbin/mysql/bin/mysqld(ZN7handler13ha_update_rowEPKhS1+0x228)[0xaaaae0a61014]
/rdsdbbin/mysql/bin/mysqld(_ZN21Update_rows_log_event11do_exec_rowEP14rpl_group_info+0x234)[0xaaaae0b5c174]
/rdsdbbin/mysql/bin/mysqld(_ZN14Rows_log_event14do_apply_eventEP14rpl_group_info+0x25c)[0xaaaae0b5115c]
/rdsdbbin/mysql/bin/mysqld(_Z39apply_event_and_update_pos_for_parallelP9Log_eventP3THDP14rpl_group_info+0x144)[0xaaaae07d3e0c]
Printing to addr2line failed
/rdsdbbin/mysql/bin/mysqld(+0x99ede8)[0xaaaae099ede8]
/rdsdbbin/mysql/bin/mysqld(handle_rpl_parallel_thread+0xa14)[0xaaaae09a3134]
/rdsdbbin/mysql/bin/mysqld(+0xea8730)[0xaaaae0ea8730]
/lib64/libpthread.so.0(+0x722c)[0x40002459f22c]
/lib64/libc.so.6(+0xd4a1c)[0x4000246a1a1c]

After digging around, this looks like an old bug that was fixed - https://bugs.mysql.com/bug.php?id=53390. Verified there are no BLOB columns being used either.