all: update gopkg.in/yaml.v2 7ad95dd0798a => v2.2.2

[leighmcculloch]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with name of package that is most changed in the PR, ex.
  services/friendbot, or all or doc if the changes are broad or impact many
  packages.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated any docs (developer docs, .md
  files, etc... affected by this change). Take a look in the docs folder for a given service,
  like this one.

Release planning

• I've updated the relevant CHANGELOG (here for Horizon) if
  needed with deprecations, added features, breaking changes, and DB schema changes.
• I've decided if this PR requires a new major/minor version according to
  semver, or if it's mainly a patch change. The PR is targeted at the next
  release branch if it's not a patch change.

Summary

Update gopkg.in/yaml.v2 for transition to Modules (#1634).

From: gopkg.in/yaml.v2@7ad95dd0798a
To: gopkg.in/[email protected]

Diff: go-yaml/yaml@7ad95dd...v2.2.2 (96 commits)

Goal and scope

To make the transition to Modules possible. Some dependencies at their current version have incompatible relationships with other dependencies we have. Dep was more tolerant to incompatible versions than Modules. Making this change ahead of the PR that switches us to Modules makes that PR a functional no-op.

The reason Modules is updating yaml.v2 is because the monorepo is also dependent on github.com/onsi/gomega which had to be upgraded due to another dependency requirement. The version of gomega we're using is explicitly dependent on at least v2.2.1 of yaml.v2 requiring us to update to a newer version.

I'm taking the dependency all the way to v2.2.2 which is the latest patch release. While I don't understand all the changes deeply in the diff, the changes don't appear to be significant.

As a bonus these newer versions of yaml.v2 are released under a more desirable license, Apache License 2.0. The commit we were dependent on previously was released under LGPL 3.

Summary of changes

• Change the version of the package to the version that Modules selects.

Known limitations & issues

N/A

What shouldn't be reviewed

N/A

[accordeiro]

This makes sense to me. I wasn't able to find anything in that diff that looked like a breaking change either, nor to find any mention of API changes in their GH releases. Approving :)