[WIP] Introduce generic execution engine

[lukmzig]

Changes in this pull request

Added generic execution engine

Additional info

For discussion:

• How to handle storage of succeeded/processed elements? Is a column in the table, that gets reset enough? Or should it be stored in a separate table? - It is ok for now
• Log to different/separate file? - added separate channel
• Does it make sense to execute step 2 after step 1 was executed? Even with continue on error option? Theoretically you could also achieve this with 2 different jobs - not needed right now
• Create events for different actions, e.g. job startet, job completed, job state, ...

[github-actions]

Review Checklist

• Target branch (11.2 for bug fixes, others 11.x)
• Tests (if it's testable code, there should be a test for it - get help)
• Docs (every functionality needs to be documented, see here)
• Migration incl. install.sql (e.g. if the database schema changes, ...)
• Upgrade notes (deprecations, important information, migration hints, ...)
• Label
• Milestone

[sonarcloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud