Workflow for building and publishing images

[schneiderfelipe]

I propose:

• Image builds on PRs and on pushes/merges to master
• Publishing on pushes/merges to master

This ensures we don't publish problematic images and the master branch is always up-to-date and passing builds.

This will require two GH actions.

[Leticia-maria]

Okay @schneiderfelipe, thank you for opening the discussion as an issue. I'll check this out and solve it. I also suggest correcting the build sequence. I mean, only build the updates, not all the images every time we change something. This takes a lot of running time, as you can see in the GH actions logfile.

• Build only when Dockerfiles are updated
• Not build all the images to verify a PR

[Leticia-maria]

• Create a separate workflow to build a PR