CI: Separate deploy and test

[tischi]

@constantinpape

Here we should also think about refactoring the CI.

Here, however, I think we would need also the SNAPSHOT versions to be deployed to maven, otherwise I think we will run into such issues: https://github.com/mobie/mobie-viewer-fiji/actions/runs/4806700915, where the build on develop failed because it did not have the most recent mobie-io version...

Thus maybe it is OK as it currently is, what do you think?

[constantinpape]

If we are fine with running the deployment on pushing to develop as well (for pushing the SNAPSHOTS) then I don't really think we need to change anything in the current yaml, see https://github.com/mobie/mobie-io/blob/main/.github/workflows/build.yml#L7.

But I think we should add another test.yaml that only runs the tests for pull requests onto develop, so that we know beforehand if those break anything. For this you should be able to more or less copy what we did for mobie-fiji: https://github.com/mobie/mobie-viewer-fiji/blob/develop/.github/workflows/test.yml

[KateMoreva]

Simple realisation is here #145

test-> will work for pull_request to main or develop
run mvn test (works)

build-snapshot -> will work only for pull_request to develop or push to develop with tag *.[0-9]-SNAPSHOT
run mvn test + .github/build.sh (seems to work)

deploy-main-> will work only for push to develop or main with tag [0-9].[0-9].[0-9]
run mvn test + .github/build.sh (not tested yet)

[tischi]

@imagejan may I ask your help to also check for this repo whether the CI is set up correctly?