Use 'yaml.v3' (2nd try)

[inteon]

Continuation of #100

Switches from the 'yaml.v2' fork to the 'yaml.v3' fork. Tried to do this while maintaining backwards compatibility as much as possible.

Fixes some of the Yes = true and No = false confusion (see tests).

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: inteon
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[inteon]

"Will this result in visibly different output? Any changes have the potential to break consumers so we need to be extremely careful about changes that break byte-for-byte round-tripping" - @liggitt

#100 (comment)

[inteon]

Afaik, this should just result in float64 values also being supported.
I added a few additional test cases for float marshalling and unmarshalling.

[dims]

fyi, once #133 lands, you will need to revisit this PR.

[liggitt]

fyi, once #133 lands, you will need to revisit this PR.

(even once reworked on top of that, it's still not clear to me that the things this changes / breaks will be feasible to overcome and roll out ... the unknowns about switching to v3 are super time-consuming to chase down definitively ... I appreciate the continued effort here, it's just really difficult to prioritize almost unbounded due diligence work to review / approve this)

[k8s-ci-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ingydotnet]

There are current (albeit tentative) plans to make the v4 API configurable to a very granular level.

If we can get the v4 API to work exactly the same way given a v2 configuration, then I think it will be possible for users to add very specific new v4 features to their configs.
(Rather than needing to buy into every change that v3 made from v2).

[ingydotnet]

I'll mention this PR in the yaml/go-yaml v4 config PR when it lands, so people here can be aware and weigh in...