Add rules to pipelines

After a discussion in BBB, we agreed on the following:

1. One pipeline runs at every commit, but just builds a container and runs the unit tests. So you can quickly check, if you messed something up

2. One pipeline runs on a merge request with everything related to code. So build, test and integration tests. Licensing also runs, but only when a dependency is added or updated

3. Nightlys get removed, as they don't test new things. Only the security and compliance pipelines are run nightly to generate the statistics.

4. MR to develop pipeline with integration test

   • licensing only if go.mod or go.sum were edited

Description

Expected Behavior

Actual Behavior

Possible Fix

Steps to Reproduce

Context

Your Environment

• Version used:
• Environment name and version (e.g. go v1.16.3 on FreeBSD 13.0-current):
• Server type and version:
• Operating System and version: