InnoDB changes between mysql-8.4.6 and mysql-8.4.7

Note: mysql-8.0.43 (MDEV-37371) was the last release in that series.

Not applicable to MariaDB Server

Bug#37003342 Confusing warning "Cannot add field x in table y because after adding it ..."
This change is not directly applicable to MariaDB, but there is an open bug MDEV-16969 about something similar.
Bug#38142283 Compile MySQL with clang 20 (follow-up)
MariaDB Server is already being successfully built with clang 20.
Bug#37792010: read from performance_schema.data_locks causes the server to exit abnormally
The fix does not look acceptable to me, and there is no test case. It is unclear whether there is a bug that could affect MariaDB. This will be tracked in MDEV-36545.
Bug#37882398 Assertion failure: ddl0file-reader.cc ...
This is related to a feature that is yet to be implemented in MariaDB (MDEV-16281).
Bug #38167527 Virtual Index Rollback Fails on 32-bit Build
This was already fixed in MDEV-36613.
Bug#37602657 virtual index corruption
This had been fixed in MDEV-12353. The most relevant changes are to the functions row_upd_index_parse() and row_upd_index_parse() and to the way how the index metadata is being written to and parsed from the redo log. Starting with MDEV-12353, MariaDB would emit low-level WRITE records for such changes. The fix includes quite a bit of irrelevant reformatting and is convoluting some MDEV-5800 related data structures further, to the opposite direction from what I think should be done in MDEV-22363.
Bug#37994397 Startup with upper limit of bp size
The logic around innodb_buffer_pool_size was rewritten in MDEV-29445.
Bug#38325137 Assertion failure row0pread.h:306:active >= n_threads happens when create thread fail for parallel scan
In MariaDB Server outside Columnstore, there is no parallel query processing yet (MDEV-6096, MDEV-18705, MDEV-21291).