Make CI pipelines the same across projects

[stevenbal]

Not sure if this repo is the right place for this issue, but I noticed that Open Zaak has an image_scan job in the CI pipeline: https://github.com/open-zaak/open-zaak/blob/main/.github/workflows/ci.yml#L268. Is this something we want in the other projects as well?

In general, I think it is a good idea to check if the pipelines are the same (or at least as close as possible) and up to date when it comes to versions for actions

• Add the best things to the default project - api folder.
• Make sure all the API projects have similar CI pipelines

[stevenbal]

Maybe we could make use of https://github.com/maykinmedia/setup-django-backend/tree/v1.3

[SonnyBA]

A first effort to make the CI pipelines more consistent was made through open-zaak/#1730. The code quality workflow was used for this and now reuses the code quality workflow from the open-api-workflows repository.

[SonnyBA]

Moving the workflow files to the root repository does not seem possible (screenshot taken from an open-zaak run):

[SonnyBA]

• Open-zaak
  • [#13] add check_schema script & reuse open-api-workflows workflow open-zaak/open-zaak#1730
• Open-Klant
  • [#13] reuse open-api-workflows workflows open-klant#238
    • Requires a new release of OAF, see Add missing authorizations app for commonground-api-common #70
• Referentielijsten
  • [#13] reuse open-api-workflows workflows referentielijsten#30
• Objects-API
  • [#13] reuse open-api-workflows workflows objects-api#447
• Objecttypes-API
  • [#13] make CI jobs more consistent with open-api-framework related projects objecttypes-api#129
• Open-Notificaties
  • [#13] reuse open-api-workflows workflows open-zaak/open-notificaties#189