chore(deps): bump github.com/google/go-cmp from 0.3.0 to 0.5.9

[dependabot]

Bumps github.com/google/go-cmp from 0.3.0 to 0.5.9.

Release notes

Sourced from github.com/google/go-cmp's releases.

v0.5.9

Reporter changes:

• (#299) Adjust heuristic for line-based versus byte-based diffing
• (#306) Use value.TypeString in PathStep.String

Code cleanup changes:

• (#297) Use reflect.Value.IsZero
• (#304) Format with Go 1.19 formatter
• (#300 )Fix typo in Result documentation
• (#302) Pre-declare global type variables
• (#309) Run tests on Go 1.19

v0.5.8

Reporter changes:

• (#293) Fix printing of types in reporter output for interface and pointer types
• (#294) Use string formatting for slice of bytes in more circumstances

Dependency changes:

• (#292) Update minimum supported version to go1.13 and remove xerrors dependency

v0.5.7

Reporter changes:

• (#266) Fix textual printing of byte slices
• (#275) Reduce minimum length for specialize string diffing
• (#276) Use any alias instead of interface{}

Code cleanup changes:

• (#281) Update minimum supported version to go1.11
• (#282) Drop hacks to work around Go reflection bugs in Go1.9
• (#285) Add //go:build lines
• (#262) Fix staticcheck findings
• (#263) Avoid shadowing variable
• (#268) Use sha256 in test
• (#271) Fix spelling mistakes
• (#269) Change build status badge

v0.5.6

Reporter changes:

• (#258) Print as text if mostly text
• (#259) Cleanup edit groups after coalescing
• (#260) Avoid diffing by lines if inefficient

Minor documentation changes:

• (#256) Fix typo in path.go

v0.5.5

... (truncated)

Commits

• a97318b Adjust heuristic for line-based versus byte-based diffing (#299)
• 377d283 Run tests on Go 1.19 (#309)
• 6606d4d Use value.TypeString in PathStep.String (#306)
• f36a68d Pre-declare global type variables (#302)
• 5dac6aa Fix typo in Result documentation (#300)
• 14ad8a0 Format with Go 1.19 formatter (#304)
• a53d7e0 Use reflect.Value.IsZero (#297)
• f144a35 Additional cleanup with Go 1.13 as minimal version (#295)
• 63c2960 remove xerrors (#292)
• 71220fc Use string formatting for slice of bytes (#294)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[jenkins-x-bot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 jenkins-x/lighthouse repository.

[garethjevans]

/ok-to-test

[garethjevans]

/lgtm

[jenkins-x-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: garethjevans

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [garethjevans]

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

[jenkins-x-bot]

New changes are detected. LGTM label has been removed.