Move all non-prod installation checks to GH Actions

[regDaniel]

In the future, we suggest to use Jenkins exclusively for testing production installations (pinned, non-editable). Dev and/ or unpinned installations should be tested through GH actions as available resources through our organization repo allow us to do so.

[bascrezee]

Sounds good to me. I did have a bit of doubt when thinking about unit tests relying on test datasets which are not included in the repository (as is the case currently for kenda_python). However, this should be fine, while testing, one can check the machine, and skip unit tests for which test data is not available on that machine. For those unit tests, which are skipped by GH actions, one would fully rely on the production installation test by Jenkins. Just wanted to mention it, to keep this use case in mind.