Add tests of simtools-prod containers

[GernotMaier]

Add a test for the simtools-prod container to ensure that everything is correctly installed. For this, run a single application test using the database and sim_telarray (simtools-simulate-prod).

This required to separate the steps of generating the container and pushing.

The successful github action workflow for the container generation do not appear below, it is:

• simtools-prod: https://github.com/gammasim/simtools/actions/runs/7210340303/job/19643252445
• simtools-dev: https://github.com/gammasim/simtools/actions/runs/7210340303/job/19643252194

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (a5bd97a) 82.18% compared to head (88ebde4) 82.22%.
Report is 1 commits behind head on main.

❗ Current head 88ebde4 differs from pull request most recent head c93b4e9. Consider uploading reports for the commit c93b4e9 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #713      +/-   ##
==========================================
+ Coverage   82.18%   82.22%   +0.04%     
==========================================
  Files          42       41       -1     
  Lines        6196     6210      +14     
==========================================
+ Hits         5092     5106      +14     
  Misses       1104     1104              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[GernotMaier]

And I notice now that the docker-simtools test start when pressing "read for review".

[orelgueta]

You are using the config file that comes in tests/resources for running, but do we expect that the production container comes with the tests directory? It probably shouldn't, no?

If we decide to remove tests from this container, we can just provide the arguments directly, they are not too many.

I approve anyway cause the solution works for now.

(As a side note, the amount of commits and their messages for such a small change show how much of a pain it is to work on docker stuff.)

[GernotMaier]

No, the tests directory is not part of the container. It is available in the workflow, because we need to do a checkout of simtools to get the Dockerfile. Using the config file simplifies this - and if we change any of the command line parameters we do not have to worry about this test (unless we change the --config parameter.

[orelgueta]

Oh yea, I forgot this is part of building the container and therefore we need to checkout simtools anyway. All good then.