Currently most of the tests in `source/tests` rely on Python scripts, this is fine, but there are areas of our C api we probably wont expose to python and we still want to be able to test them.
eg: https://developer.blender.org/diffusion/B/browse/master/source/blender/blenlib/BLI_path_util.h
An example of where testing would be useful is for checking UNC paths, (ms-windows `\\network\paths`). don't break other use cases when the patch is applied. [0].
This task is to evaluate how best to manage testing C API (Mostly BLI and BKE functions)
[0] https://developer.blender.org/D298
//Note, exactly how C/C++ tests are compiled and setup should be done with some care, since it should work across many different modules.//