[Feat] Add update GitOps repository workflow

[saenyakorn]

Why did you create this PR

What did you do

• Add update-gitops.yaml workflow for open PR to cugetreg-gitops repo
• Add gitops-mode to choose between PR or commit

Workflow explain

• When we push something to to dev, the action will calculate affected packages and push kustomize changed to gitios repo.
• When we push something to beta, the action will do pre-release thing, and then open the Pre-release PR. After we merge the PR, the action will bump the package version, build the docker images and open kustomize changed PR to GitOps repo.
• Similar to beta, when we push something to main, the action will do release thing, and the rest is the same as beta's flow.

Demo

Workflow https://github.com/thinc-org/cugetreg/actions/runs/4106806503

Success Commit - https://github.com/thinc-org/cugetreg-gitops/commit/ac296cee9f9ada87fc91369eda675950bbcbd62f

Success opened PR - https://github.com/thinc-org/cugetreg-gitops/pull/6

https://dev.cugetreg.com

Checklist

• Deploy a demo
• Check browsers compatibility
• Wrote coverage tests

[changeset-bot]

⚠️ No Changeset found

Latest commit: 737947d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[suphon-t]

One more thing. The old syntax seems to be broken.