Our settings refuse to merge if no pipeline has been run.

The deploy_gitlab_ci now creates the integration commit and branch in
each passed subproject and create an integration commit in the manifest
containing all these new revisions.
A build is then triggered on this commit to test the functionality.

Split the update_submodule functions to reuse them in different ways.
Remove some previously used files.

BCS 746-000740

Added additional log output for sdk upload.

Remove alphaplan_fwr debug code and run black and pylint.

To improve the readability of the package_release.py script.

BCS 746-000734

Now md5sums.txt can be assembled from different copy processes.
The build md5sums file is not overwritten by the license copy process
anymore.

BCS 746-000637 746-000734

The alphaplan FWR generation is now separated to make the manifest gitlab-ci
file more easy to understand and reduce the complexity of the
package_release file.

BCS 746-000637

The merge job of a subproject include in the merge request merged by
gitlab ci, should not merge the integration branch in the manifest by
themself. This is now disabled by checking the source branch name.

This allow to merge the manifests commit at last.

Tim suggested to use the same name scheme for all jobs and use the group
names yocto and gitlab-ci as base.

Initially the moved code was needed to create the files including the
new implementation.

Also set yocto deploy job to manual to test merge.

For projects like the kernel the git checkout needs a log of time and
space. Directly using the gitlab api only loads the infomation needed.

Integrates the changes done in the foobar- yml files to the yocto
projects.

This change should be reverted after once used.
It is needed to initially add the include .gitlab-ci.yml in
all subprojects.

As all projects are commited in the same branch the 'up-to-date' check
may not only check if the first parent commit points to the
master/dunfell branch. Now it is needed to loop through the history
until the integration branch's commit is found.

On fail a message is displayed which merge request needs to be
retriggered manually. This can now also be the 'parent'-MR that
triggered the complete chain.

The check job is used pipeline again.

The retrigger job also looks in the .gitlab-ci project for check jobs to
retrigger.

BCS 746-000646