#32: vt-tv: Improve CI

[tlamonthezie]

Fixes #32
Fixes #92
Fixes #103
Might fix #69

Important! Dockerhub repository is modified from that PR (now same that vt one). Base docker images are used for unit tests and are not already pushed to the new repository which will generate failures on CI until merge is done.

One of the latest run (using old repository) can be found at https://github.com/DARMA-tasking/vt-tv/actions/runs/10177046856

After merging please call the pushdockerimage action to push base images (with VTK) to the new Dockerhub repository. Until that CI will fail

This PR includes:

Unit tests refactoring and writing:

1. Remove obsolete code in the tests & example directories
2. Move GoogleTest and its & fetch script to lib directory + update the fetch script.
3. Re-organize the tests directory and update CMakeLists under tests/unit and build tests in a single executable for Google test optimal use.
4. Add unit tests mainly for the api classes
5. Add TESTING.md documentation to get started with testing.
6. Add root build.sh script capable for local use as well as for ci use with some options for build, coverage and test run. get more info with build.sh --help. This provides for example a way to generate coverage html report, JUnit report etc.
7. Add simple diff test for CCM example PNG output with some tolerance. See tests/test_image.sh (Call internally a python module for now to diff between actual and expected png image). (This is called by the ParseRenderTest class after rendering with the ccm_example0.png generated file).
8. Remove ctest calls to use only GTest directly (Test compiled in a file)
9. Reorganize tests data files and config files and re-generate lb_synthetic_data using the create_synthetic_attributes_data.py script (and reorganize generated attributes alphabetically in the python script)

CI:

1. Add xvfb as graphics display in CI.
2. Make python bindings test working in CI and include in the Build & Test pipeline workflow (remove test bindings workflow). See ci/docker/build-and-test.dockerfile and called shell script for details.
3. Include Test results & Coverage in Github step summary of job run.
4. Upgrade external used github actions (some versions were deprecated)
5. Make docker image configurable (base image, compiler, VTK version, Python version).
   5.1 Configurable base image: ci/docker/make-base.dockerfile used by the .github/workflows/pushbasedockerimage.yml . The pushbasedockerimage contains now an input to select the image to build and push to DockerHub.
   5.2 Configurable vt-tv build & test image ci/docker/build-and-test.dockerfile used by the .github/workflows/build-and-test.yml workflow
   5.3 Provide test matrix using the 3 images in the build & test workflow:
   • ubuntu_22.04-gcc_11-vtk_9.2.2-py_3.8 (Build, Test)
   • ubuntu_22.04-clang_14-vtk_9.2.2-py_3.8 (Build, Test)
   • ubuntu_22.04-gcc_12-vtk_9.3.0-py_3.8 (Build, Test, Coverage)
6. Add CMake options (enable tests, enable coverage)

Because docker images are more scalable it will be easier to add later additional configurations to the pushbasedockerimage.yml workflow and to add it to tests in the build-and-test.yml images to build vt-tv on and to run tests on.
Additionnaly the ci folderhas been re-organized and docker images are now in the newci/docker` directory

Additionally added fix from #92 to make checks successful for clang.

[cwschilly]

Mostly minor changes--everything looks great on the whole. I do think we should test the content of the mesh files though.

[ppebay]

Please create follow-on issues @tlamonthezie for aspects that are not covered yet by CI but that we discussed at last meeting.

[tlamonthezie]

Please create follow-on issues @tlamonthezie for aspects that are not covered yet by CI but that we discussed at last meeting.

Hi @ppebay I created an issue to continue to work on the CI/Tests see #95 . Some additional things than those discussed have also been added.

[nlslatt]

This is a huge PR. You might consider breaking it up into multiple PRs if it gets difficult to get everything passing.

[nlslatt]

I noticed that style varies from file to file and I wonder if we should implement vt's style guidelines here as well, perhaps as a separate PR so we can get this merged sooner rather than later.

vt has a tool that will check/correct the header comments at the tops of files, including setting the correct filenames. There are more files that need to be corrected than I marked.