build(deps): bump github.com/evanphx/json-patch from 5.7.0+incompatible to 5.9.0+incompatible

[dependabot]

Bumps github.com/evanphx/json-patch from 5.7.0+incompatible to 5.9.0+incompatible.

Release notes

Sourced from github.com/evanphx/json-patch's releases.

v5.9.0

What's Changed

• Validate that the partialDoc is decoded correctly by @​evanphx in evanphx/json-patch#201
• Add option to control if the output is HTMLEscaped by @​evanphx in evanphx/json-patch#202

Full Changelog: evanphx/json-patch@v5.8.1...v5.9.0

Fix API breakage

This PR fixes Operation containing a reference to internal/json and breaking the ability to manually compose one. This restores that ability using a type alias.

Full Changelog: evanphx/json-patch@v5.8.0...v5.8.1

Blargh Phixs and Empathyprovements

This release fixes a few stray panics, addresses large number accuracy, and improves performance!

What's Changed

• Compare strings after decoding them to handle unicode correctly. Fixes #172 by @​evanphx in evanphx/json-patch#195
• Always use UseNumber() to avoid float64 lossyness by @​evanphx in evanphx/json-patch#194
• Handle null correctly when introduced by replace. Fixes #171 by @​evanphx in evanphx/json-patch#196
• Handle from="" more properly. Fixes #192 by @​evanphx in evanphx/json-patch#193
• Improve performance by @​evanphx in evanphx/json-patch#197

Full Changelog: evanphx/json-patch@v5.7.0...v5.8.0

Commits

• b7a4e4a Merge pull request #202 from evanphx/f-html-escape
• 7eef36c Guard using options to avoid a crash bug
• 1bcbd0f Merge pull request #201 from evanphx/b-null
• 9d7ba23 Add option to control if the output is HTMLEscaped
• 009bc56 Validate that the partialDoc is decoded correctly
• b82b685 Use a type alias for RawMessage to avoid breaking the public API of Operation
• 05c9526 Merge pull request #197 from evanphx/f-perf
• 7a438a6 Minor simplifications
• 2a122d1 More optimizations
• 174e1d7 Add MergePatch benchmark
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[openshift-ci]

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

I'm waiting for a operator-framework 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 kubernetes-sigs/prow repository.

[grokspawn]

/ok-to-test