arrow: add run_tests.sh

[DavidKorczynski]

run_tests.sh is used as part of Chronos with cached builds: https://github.com/google/oss-fuzz/tree/master/infra/experimental/chronos#check-tests

$ infra/experimental/chronos/check_tests.sh arrow c++
...
...

33/46 Test #36: arrow-json-test ....................   Passed    1.56 sec
34/46 Test #32: arrow-feather-test .................   Passed    3.06 sec
35/46 Test #26: arrow-utility-test .................   Passed    3.49 sec
36/46 Test #39: parquet-reader-test ................   Passed    3.57 sec
37/46 Test #23: arrow-io-compressed-test ...........   Passed    5.50 sec
38/46 Test #38: parquet-encoding-test ..............   Passed    5.30 sec
39/46 Test #20: arrow-compute-scalar-cast-test .....   Passed    7.04 sec
40/46 Test #27: arrow-async-utility-test ...........   Passed    8.69 sec
41/46 Test #42: parquet-arrow-reader-writer-test ...   Passed    8.41 sec
42/46 Test #29: arrow-threading-utility-test .......   Passed    8.76 sec
43/46 Test #41: parquet-chunker-test ...............   Passed    8.71 sec
44/46 Test  #1: arrow-array-test ...................   Passed    9.60 sec
45/46 Test #34: arrow-ipc-read-write-test ..........   Passed    9.52 sec
46/46 Test #40: parquet-writer-test ................   Passed   18.53 sec

100% tests passed, 0 tests failed out of 46

Label Time Summary:
arrow-compute-tests    =   7.36 sec*proc (2 tests)
arrow-tests            =  63.05 sec*proc (34 tests)
parquet-tests          =  48.01 sec*proc (10 tests)
unittest               = 118.42 sec*proc (46 tests)

Total Test time (real) =  18.97 sec
--------------------------------------------------------
Total time taken to replay tests: 19

[pitrou]

Hi @AdamKorcz @DavidKorczynski , I'm a Arrow maintainer and I would be curious to know: what is the point of running unit tests here? Does it inform the fuzzer in any way? I could not find any documentation explaining this.