* The filesystem artifact name now match the image name
* Fix on artifacts name from build and deploy stage

* Insert further variable inheritance for edgehog-embedded jobs
* Insert echo messages for debug

* Fix also on artifacts name construction

* The fix introduce the RECIPE_NAME variable in the job/link log name,
necessary when compiling also embedded distro

* Change "edgehog-base-image" label to "edgehog-things-image" one
* Fix on intel_apl config file
* Fix on AZURE_PATH variable (the edgehog folder is necessary
for the public container release)

* Insert edgehog embedded build/deploy for base and full image for supported
boards
* Full image shall be built only when a tag occurs
* Remove c43 and c26 config files (not yet supported)
* Fix on Link_report.txt

* Change all occurrencies of 'yocto_ng' with 'edgehog' due to group
 rename
* Change all occurrencies of 'kirkstone/develop' with 'kirkstone' due
to master branch rename
* Update documentation references accordingly
* Changelog script loops over MR opened both to 'kirkstone/develop' and
'kirkstone' branch
* Minor fix in notify job

* Add intel_apl support inside main .yml file
* Include changelog.md file inside the notify (the file is both uploaded
to Azure and accessible via the Teams notification)
* Insert release stage allowing to create a GitLab release when a tag is
created containing all the links to access built artifacts and changelog

* Modify script for changelog generation
* Insert job to create changelog for testing purpose

Merge branch 'manifest_branch_fix' of git.seco.com:yocto_ng/infrastructure/gitlab-ci into manifest_branch_fix

* This variable allows to define the branch that is used for the
manifest build (the master one on schedule/tag or the integration one on
upstream pipeline trigger)

* This variable allows to define the branch that is used for the
manifest build (the master one on schedule/tag or the integration one on
upstream pipeline trigger)

* Partial testing of correct NXP repository integration

* The script is a direct derivation of the original one and can be
merged in a near future
* The script search for the latest updated MR in the project repository
to retrieve the source branch
* Then merge the MR on the layer project according to the recontructed
integration branch

* This commit adds the script to check if the integration branch is
up-to-date on the layer side
* Very few modification with respect to the original script
* The script can be merged with the original one in the near future

* The script is derived from the integrate_into_manifest file and is
used to create the integration branch on layers
* The script create a new branch with the modifications on the
SRCREV.conf indicated as parameter and on the bitbake recipe indicated
* In a future this file could be merged with the integrate_inot_manifest
one

* The file is intended to contain all the automation tasks to be
executed by the projects used in the Yocto layers
* The steps are the main steps that this CI file contains:
  - Every time a MR is opened on a project an integration branch is opened
 on the layer which updates the SHA of the commit on the
'conf/SRCREV.conf' file referring to correct bb recipe
  - A MR is automatically opened on the layer master branch, that triggers all the
downstream job of the manifest-integration file, which is left untouched
  - A check job checks that the layer project branch is up-to-date with
the commit revision
  - Once the MR is accepted on the project, the one in the layer is
merged and closed by default after having tried a rebase.
* Minor bug fix on gitlab-ci.yml file

* The script is identical to the 'scripts/deploy_gitlab_ci_projects.py'
apart from the fact that does look for a manifest project to
integrate/merge
* In the future the two scripts may be merged to treat both cases
correctly, for now we skip this part

* The .gitlab-ci submodule is added also to other groups (those
containing kernel, uboot, etc.) so it is necessary to create an
integration branch also them

* The variable is necessary when the GitBot will be given access to
sveral groups to restrict the search for the manifest repository
* Add --verbose option and other debug stuff in merge job

* The SW artifacts with the same name are overridden
* Bug fix on notification.json file search

* Bug fix on Azure path

* When a tag occurs the '-b' command in repo init would fail

* Insert trigger rule allowing to build/deploy/notify on tag creation
* In deploy-on-tag job the artifacts are uploaded to the official SECO Azure
container with dedicated token, stored as 'yocto_ng' group variable
* The commit should fix the error in notify job

* The job will be taken in charge by the runner with 'infrastructure'
tag