* 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)

* 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

* Change syntax rule

* Change syntax rule

* This commit insert the schedule in the workflow rules allowing to trigger build, deploy, notify on a scheduled basis
* Bug fix on variables

* The build job is now triggered on schedule

* Without this fix the branch used for the build is always the
kirkstone/develop one

* The jobs will be uncommented in the next future for testing purpose

* Update README.md and files in the doc folder to fit the new version
 of CI/CD config files
* Update variables in common file to fit the newly created Docker images
* Insert C31 board build and deploy jobs
* Remove files used in previous integration tests