Today creating a backmerge MR from prod or integ branch to any other branch triggers a pipeline
even though no change has been pushed.
Ultimately those pipelines might (re)trigger integration or production environment deployment and/or packages publication.
That might have unexpected consequences.
This change simply disables MR pipeline from prod & integ branches, enforcing branch pipelines only (i.e. when a true commit is pushed).

chore(deps): update dependency to-be-continuous/semantic-release to v3.8.2

See merge request to-be-continuous/tools/template-skeleton-2!4

chore(deps): update dependency to-be-continuous/bash to v3.4.0

See merge request to-be-continuous/tools/template-skeleton-2!2

chore(deps): update dependency to-be-continuous/semantic-release to v3.8.0

See merge request to-be-continuous/tools/template-skeleton-2!3

Configure Renovate

See merge request to-be-continuous/tools/template-skeleton-2!1

rewrite all '$SOME_VAR' test expressions to '($SOME_VAR != null && $SOME_VAR != "")'

 requires GitLab 16.6 or later