Fix can't find mvn

[radumereuta]

I'm hoping this is why it can't find mvn.

Right now the jammy deploy fails with

+ docker exec -t k-package-docker-test-jammy-5dde91161befd1f004ba0af7b8527e0616ae799c bash -c 'mv /tmp/settings.xml ~/.m2/settings.xml'
+ docker exec k-package-docker-test-jammy-5dde91161befd1f004ba0af7b8527e0616ae799c /bin/bash -c 'mvn --batch-mode deploy'
/bin/bash: line 1: mvn: command not found
Error: Process completed with exit code 127.

[ehildenb]

This change seems nice for uniformity, but I don't think it will fix the issue. I don't see maven listed in the Docker image we're using here for testing:

k/package/docker/Dockerfile.ubuntu-jammy

Line 8 in 5dde911

&& apt-get install --yes \

, or in the runtime dependencies of K framework package:

k/package/debian/control.jammy

Line 13 in 5dde911

Depends: bison , clang-14 , default-jre-headless , flex , gcc , g++ , libboost-dev , libffi-dev , libfmt-dev , libgmp-dev , libjemalloc-dev , libmpfr-dev , libtinfo-dev , libyaml-0-2 , libz3-4 , lld-14 , llvm-14 , pkg-config

I don't think we really want to put it in either of those places, because we want to test that the package works without having the build system present. So really, we should be doing the deployment of the java artifacts from a different docker container, probably from the docker container that is used for main testing: https://github.com/runtimeverification/k/blob/master/.github/workflows/Dockerfile

I would suggest:

• Pull out the mvn deploy into it's own job, instead of mixing it into the Dockerhub image build job.
• Have that use the with-docker action, which you can see examples of using that in other places in the repo, and that will use the linked Dockerfile at .github/workflows/Dockerfile, which does have maven installed.