Add war deployment check

[MichaelsJP]

Currently, the war deployment is not checked. This starts the container and waits for the health API to indicate the default graph is built and ready.

Pull Request Checklist

• 1. I have [rebased][rebase] the latest version of the master branch into my feature branch and all conflicts
  have been resolved.
• 4. I have removed unnecessary commented out code, imports and System.out.println statements.
• 8. I have built graphs with my code of the Heidelberg.osm.gz file and run the api-tests with all test passing
• 9. I have referenced the Issue Number in the Pull Request (if the changes were from an issue).
• 12. I have written in the Pull Request information about the changes made including their intended usage
  and why the change was needed.

Closes #1355

Information about the changes

• Key functionality added: Test for correct war deployment.

[jlink]

Does it work - asking because the build step seems to be hanging.

I don't understand all the details of the new build step, what strikes me is that the test will only be run on CI. That's rather late feedback. If that's ok, depends on how often we expect a problem with the war deployment.

[MichaelsJP]

@jlink

Does it work - asking because the build step seems to be hanging.

Yes. The action name has changed, and it's still looking for the old. Will change that before the merge. Else, all other PRs will have to wait for it.

I don't understand all the details of the new build step, what strikes me is that the test will only be run on CI. That's rather late feedback. If that's ok, depends on how often we expect a problem with the war deployment.

I'm open to ideas on how to solve that deployment scenario locally, as isolated as it is in the workflow with the Dockerfile. In my opinion, it's ok to have that kind of feedback latest with a PR, so there is no danger of merging it into master. It also runs on a draft PR, so feedback is given quick if commits are uploaded regularly.

[jlink]

Let's start with your approach and think about a way to extract that from GH actions later.