Migrate from ghodss/yaml to sigs.k8s.io/yaml

[antgamdia]

Description of the change

This PR just replaces ghodss/yaml with Kubernetes fork of the same library, sigs.k8s.io/yaml, as it was the most used along our codebase.

Benefits

Reduce same-purpose deps.

Possible drawbacks

I don't know we are ever relying on a very specific feature of the original dep whose behavior differs from the k8s-fork one. I can't think of it, but let's our CI decide.

Applicable issues

• rel Reduce same-purpose Go dependencies  #3848

Additional information

N/A

[absoludity]

Not sure we need to use custom names for the imports? I'd do that only where it needs disambiguation (ie. if one file imported both for some reason), otherwise, I'd avoid naming k8syaml and goyaml when there's no ambiguity in the file.

[absoludity]

Not sure we need to use custom names for the imports? I'd do that only where it needs disambiguation (ie. if one file imported both for some reason), otherwise, I'd avoid naming k8syaml and goyaml when there's no ambiguity in the file.

Oh, I should have read #4176 first, I'll reply there.