Add CPU and GPU CI tests

[sjsprecious]

What is the feature/what would you like to discuss?

As suggested by @jtruesdal , it will be great if we can add some small CI tests (e.g., FKESSLER at 1-deg resolution) and make sure each future pull request does not break the existing CPU and GPU code of NH-SE dycores in the StormSPEED CAM repo.

We can also add some ERS tests to automatically check if the answer changes or not. This would be for information only and not necessarily hold a PR being merged unless there is a clear code bug.

I expect that this workflow will work on CISL's CIRRUS cloud service.

I will break this issue into a few small tasks to ease the incremental progress:

• create a docker image with all the software stacks satisfying the StormSPEED CAM dependency.
• create a github workflow to import the docker image and build a pull request with it.
• update the previous github workflow to build and run a pull request on CIRRUS.
• update the previous github workflow with different compile types and on CPU/GPU.
• update the previous github workflow with more customized setups (e.g., compset, SMS/ERS runs) and maybe creating a test suite for StormSPEED specifically.

Is there anyone in particular you want to be part of this conversation?

@jtruesdal

Will this change (regression test) answers?

No

Will you be implementing this enhancement yourself?

Yes

[sjsprecious]

A new docker image with gcc compiler and CI workflow to build a pull request are introduced at #46.

[sjsprecious]

The CI workflow is updated to build and run the FADIAB test on CISL CIRRUS cloud server (w/ GCC compiler and on CPUs only) at #49.

[sjsprecious]

The CI workflow is updated to build and run the FADIAB test on CISL CIRRUS cloud server (GNU, Intel and NVHPC compilers, on CPUs and GPUs) at #52.

[sjsprecious]

@PeterHjortLauritzen @jtruesdal
The last task to close this issue is to have a list of tests that make sense to you two. Let me know what tests should be run regularly for a future pull request.