Adding row/column tests and benchmarks along with a benchmark/test building framework

[hyperbolic2346]

This PR adds c++ tests and benchmarks to spark-rapids-jni. The tests and benchmarks link in the helpers from cudf, so a test can be lifted directly from cudf or written in the same style as a cudf test. The benchmarks only support nvbench, as that is the preferred benchmarking tool.

To build with tests, pass -DBUILD_TESTS to the command line for the build and to build benchmarks, pass -DBUILD_BENCHMARKS. The test library used from cudf is built any time cudf is built, so no changes are necessary for that build. The benchmark library requires that benchmarks are built, so this is plumbed down through the pom.xml and build-libcudf.xml if the user selects benchmark building.

The change includes a new script build/run-in-docker that will run an executable in the same container environment that was used to build spark-rapids-jni. This script also allows an empty argument list and will drop the user into an interactive shell inside the container. This isn't a requirement, but ensures the same environment in the case the user is unable or unwilling to match the build environment.

I had to copy the 22.08 version of row_conversion.cu so the tests would properly work, but it is not quite ready to move to this repository yet.

Adding automatic running of tests after build was suggested as a feature, but left for another PR. I have added issue #330 to track it.

[jlowe]

The contributing guide needs to be updated with instructions on how to use the new build features.

[gerashegalov]

LGTM

[jlowe]

build

[gerashegalov]

Build needs more work

[2022-06-21T21:34:40.221Z] [INFO]      [exec] gmake[2]: *** No rule to make target 'libcudf.so', needed by 'libcudfjni.so'.  Stop.
[2022-06-21T21:34:40.221Z] [INFO]      [exec] gmake[2]: *** Waiting for unfinished jobs....
[2022-06-21T21:34:40.221Z] [INFO]      [exec] gmake[1]: *** [CMakeFiles/Makefile2:130: CMakeFiles/cudfjnistub.dir/all] Error 2

[hyperbolic2346]

Yes, this turned out to be a bug in the CMake Makefile Generator. I have a workaround and will update with it soon.

[hyperbolic2346]

build

[hyperbolic2346]

The workaround isn't working so well. Talking with Robert Maynard about it.

[hyperbolic2346]

build