Add GPU testing action using GitHub larger runner

[NicolasJPosey]

With the move to the UW Enterprise account, we should have access to GitHub's larger runners which include extra resources such as GPU-powered runners. This should allow us to implement tests that run on a GPU resource using GitHub Actions. I am proposing the following items to better separate the CPU- and GPU-based testing actions:

• Some of the lines of the test.yml look like they should be shared between CPU and GPU actions. Thus, we should refactor test.yml into a TestBase.yml and a CPUTest.yml.

• The "run unit tests" in the test.yml is likely just CPU tests (should be confirmed if it's not obvious) so the ./tests should be renamed to ./cpu_tests

  • This will require documentation updates in areas such as the Quick Sanity Test page that reference ./tests.

• Implement a GPUTest.yml file with a simple GPU unit test and hook up to the GPU-powered runner.

  • Implementing the GPU unit test will require adding an if(ENABLE_CUDA) block to the TESTS EXECUTABLE section of the CMakeLists.txt file.
  • We may be able to reuse the CPU pattern with GoogleTest to build the GPU unit tests at this stage.

[stiber]

I suggest breaking into 3 parts: unit tests, CPU tests, GPU tests. I agree that unit tests can just be for CPU right now.

Should also set up the actions so they only run if applicable files change. No sense in running any of these, for example, if someone modifies documentation.