feat(yaml): add advanced yamlpath support

[olblak]

Fix #1412

Thanks @mavimo for introducing me the jsonschema library and sorry that it took me so long to finish your work

This pullrequest introduces the ability to pick another Golang library for the yaml plugin.
The reasoning is the library "https://github.com/vmware-labs/yaml-jsonpath/" allows more advance yamlpath key but it is based on the go-yaml/v3 library which has many limitation.

On the other side, the Updatecli project moved to "goccy/go-yaml" which has limited yamlpath support...

So I propose an key yaml setting named engine which accept one of the following values

• yamlpath: the plugin uses "https://github.com/vmware-labs/yaml-jsonpath/"
• default, go-yaml,"": the plugin uses the goccy library

This pullrequest shouldn't introduce changes for current pipeline as we keep the current default behavior

Here is an example to retrieve a value from a specific array item in a Github Action

sources:
  getGo-Version-File:
    name: Test complex key 
    kind: yaml
    spec:
      engine: yamlpath
      file: .github/workflows/updatecli.yaml
      key: $.jobs.updatecli.steps[?(@.id =='go')].uses

Test

To test this pull request, you can run the following commands:

cd pkg/plugins/resources/yaml
go test
go build -o bin/updatecli .
./bin/updatecli diff --config e2e/updatecli.d/success.d/yaml/noscm.yaml

Additional Information

Tradeoff

Potential improvement