ci: Updater fixes for release branches (backport #756)

[mergify[bot]]

GitHub Issue (If applicable): closes #

• n/a

PR Type

What kind of change does this PR introduce?

• Project automation

What is the current behavior?

Uno Sdk Updater is really tooled to run for dev only Uno Sdk Updater runs once per hour

What is the new behavior?

Uno Sdk Updater now uses a matrix to potentially create one or more PRs for dev and stable releases Uno Sdk Updater now runs once every 6 hours. This will reduce the load on CI agents as some update PRs have triggered new builds due to a 2nd update just before the initial set of CI validations finished.

---

This is an automatic backport of pull request #756 done by Mergify.

[mergify[bot]]

Cherry-pick of e7d0964cc5c21648db5f788e04958b5497672964 has failed:

On branch mergify/bp/release/stable/5.3/pr-756
Your branch is up to date with 'origin/release/stable/5.3'.

You are currently cherry-picking commit e7d0964.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
    both modified:   .github/workflows/uno-updater.yml

no changes added to commit (use "git add" and/or "git commit -a")

Cherry-pick of 8aaa6af7fd23d7eb3128232798aab53429965ae2 has failed:

On branch mergify/bp/release/stable/5.3/pr-756
Your branch is ahead of 'origin/release/stable/5.3' by 2 commits.
  (use "git push" to publish your local commits)

You are currently cherry-picking commit 8aaa6af.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
    new file:   .github/workflows/actions/sdk-update/action.yml
    new file:   .github/workflows/uno-updater-pr.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
    both modified:   .github/workflows/uno-updater.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally