RM: test component causes new jenkins (run) instance after branch is created for release

[clemensutschig]

Describe the bug
While ods type components - create a commit with the exported state in the finalizeStage / FinalizeOdsComponent - and mark with with CI SKIP - this is not done for other component types. This causes a nasty downstream effect ... namely - that a new instance is kicked off (based on the creation of the release branch - that can do all sorts of bad things, in the best case it only fails)

To Reproduce
Steps to reproduce the behavior:

1. add a test component to your project
2. assemble a bundle for dev
3. see a NEW instance created (that is running) for the test component (release/....) - which is NOT stopping with "CI skip"

Expected behavior

1. a new instance is created with a CI skip commit in there, to omit the running

Affected version (please complete the following information):

• OpenShift: [3.11]
• OpenDevStack [master, 4.x, 3.x]

Context
https://github.com/opendevstack/ods-jenkins-shared-library/blob/master/src/org/ods/orchestration/util/MROPipelineUtil.groovy#L346-L348 - which leads to an export CI skip commit