Related to the issue: #548

Currently, when we pass in multiple packages to idpbuilder create e.g.

idpbuilder create --package https://github.com/cnoe-io/stacks//ref-implementation   --package https://github.com/cnoe-io/stacks//caipe/base

where both packages have the same yaml files:

ref-implementation/
  backstage.yaml
  backstage/manifest/
caipe/base
  backstage.yaml
  backstage/manifest/

idpbuilder will be re-queuing both files in Gitea multiple times until sync is complete, causing race condition and indeterministic behaviour which file ends up in the cluster.

As ref-implementation is a package that contains all core elements for the idpbuilder cluster to be functional, it is useful for other packages to be built on top. However, there are cases where other packages would require to modify some of the existing applications in ref-implementation such as bringing their own customised backstage.

The fix I propose in this PR adds new label "cnoe.io/package-priority" to rank the order of packages and let the later packages higher priority, much like how helm values files work. It then uses this priority to determine if the package should be written in Gitea and reconciled or not.

This is Gitea experiencing multiple re-syncing between the duplicate files in current idpbuilder:

New idpbuilder binary with the fix only updates the file once with the highest priority package: