When running tests with valgrind, one gets a lot of warnings about not freed memory.
The solution by Facebook is to add suppression, but that is likely to hide bugs and doesn't work with all memory checking tools, so we should not use this approach but instead try to fix this properly by freeing all memory at plugin unload or at least during shutdown.

I am adding temporary valgrind suppression for all the issues in 10.5 until this is fixed to be able to run valgrind on the full test suite.

Example:

mtr --valgrind mariabackup.xb_rocksdb