Github Actions workflow to build WAR, Docker, and test

[abkfenris]

Working towards building Docker images #60 this is the start of a Github Actions workflow to test ERDDAP on every push, and create a WAR that is stored as an artifact.

An example test run can be seen here (it won't run on PRs until merged or maybe approved): https://github.com/abkfenris/erddap/actions/runs/2577772040

The test job is currently failing, and the build job currently doesn't build the content.

Todo:

• [ ] Fix failing testAll job
• [ ] Build ERDDAP content zip
• [ ] Build Docker image and push to Github registry with commit SHA tag
• [ ] Push Docker image to Github registry with release tag
• [ ] Create draft release with Docker image, ERDDAP WAR and content ZIP on release tag

[abkfenris]

xref: https://github.com/BobSimons/erddap/issues/60#issuecomment-1169199421

[BobSimons]

I have rejected this pull request and approach to use GitHub Actions to do tests of ERDDAP, generate erddap.war, generate the Docker version of ERDDAP, and publish that in the ERDDAP GitHub repository. I think it is far better for Filipe and Alex to make a (semi) automated system that:

• Is triggered by someone running a script, not GitHub Actions, and thus is only run when there is a new, official ERDDAP release.
• Doesn't do any testing of ERDDAP. I have my own testing system and release checklist.
• Uses my erddap.war when I make it available.
• Has my products in my GitHub repository, and their products in their repository. That way we each have responsibility for what is in our own repository. The line of demarcation is clear. And ERDDAP-related issues will be handled in my repository and Docker-related issues will be handled in their repository.