[C++] Valgrind reports leaks from protobuf allocated memory in substrait tests #33270
Description
See https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=37514&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181&l=5635 for an example.
It's unclear to me at the moment if these are valid leaks or something we need to suppress.
It's also possible they could be prevented by running google::protobuf::ShutdownProtobufLibrary() at test shutdown.
Either way, it would be good to validate these are not legitimate issues and prevent them in some way.
Reporter: Weston Pace / @westonpace
Assignee: Percy Camilo Triveño Aucahuasi / @aucahuasi
PRs and other links:
Note: This issue was originally created as ARROW-18070. Please see the migration documentation for further details.