This uses mesh's runtime mutex for both BKE_mesh_runtime_looptri_ensure (was using its own global RW mutex before), and BKE_mesh_wrapper_ensure_mdata (was not protected at all before).

This is more like a band-aid than a proper fix, as mentioned in the report proper fix would be for the modifier to request those data (the relevant BVHTree, which would implicitely also call the tow others) through flags, just like it does for regular CDData layers. But this is a much bigger refactor to be done outside of bugfix scope.