CI: deploy job, regression around change_git_revision due to sylva_branch evolution
!9114 (merged) introduced _internal.sylva_branch and its use in CI deploy job to reliably determine the right ci-deployment-values directory to use
to make this work, I had to ensure that change_git_revision would run before sylva_ci_versioned_ci_values_folder, but I missed something: the way change_git_revision is done is that it modifies GIT_REVISION changing it from a branch name into a commit-id in some cases... this breaks the backwards compatibility code kept in sylva_ci_versioned_ci_values_folder, which derives the ci-deployment-values directory to use from GIT_REVISION...
A practical consequence of this regression is that some upgrade scenario now don't do the right thing: e.g in https://gitlab.com/sylva-projects/sylva-core/-/jobs/16479221060#L121 which is a deploy job of an "release-1.5 get transformed into a commit-id (490e307dd72503501cbeec0fb66f494a56d10d55) which prevents proper guessing that the 1.5 ci-deployment-values should be used (instead 1.6 is picked, because of the fallback to the MR target branch)
**Note that this change only impacts:
- "upgrade" pipelines that involve a branch to which !9114 (merged) hasn't been backported
- probably third-party pipelines that inherit from the sylva-core implementation of
sylva_ci_versioned_ci_values_folderto derive a CI deployment values folder from a branch or tag