Disable build-docker workflow on push to master

[MakisH]

This disables building the Docker image on push to master, which was first enabled in #186. This workflow was simply not triggered before, but currently fails #191.

Publishing such a Docker image is not needed for the system tests anymore.

@BenjaminRodenberg @IshaanDesai I am directly contributing to the master branch as a hotfix, since this only fixes (disables) the broken GitHub Actions workflow.

[MakisH]

This of course only "fixes" the GitHub view. I can also fully revert all other changes to the Dockerfile etc and revert to the previous state (which would still break if anyone tried to build for master, as before we ever touched this workflow, but one would never see that).

[MakisH]

Note also that, as I am not a maintainer of this repository, I have no idea what side-implications pushing to master has, so proceed with caution. I claim no responsibility for such side effects.

[IshaanDesai]

I do not foresee any issue right now. Pushing a hotfix directly to master should not be a problem.

[BenjaminRodenberg]

I think the main question here is what we actually want. I already discussed this to some degree with @fsimonis.

1. If we want to release docker images with the python bindings - this also implies docker images for downstream projects like the fenics adapter - I don't think this is a good solution.
2. If we only need docker images for testing, then we can probably skip the workflow for master and only regularly build a new version of precice/python-bindings:develop

My personal opinion: I can currently live without having an official docker release of the python bindings and the fenics adapter. Having the develop images is fine. With the releases on PyPI and conda I think our users also have good means to get the packages.

[IshaanDesai]

My personal opinion: I can currently live without having an official docker release of the python bindings and the fenics adapter. Having the develop images is fine. With the releases on PyPI and conda I think our users also have good means to get the packages.

✅

[BenjaminRodenberg]

@MakisH I removed some code that should now have become unnecessary. Can you do a final check and then merge?

[MakisH]

Looks good to me. You merge. :-)