deps: bump github.com/onsi/gomega from 1.43.1 to 1.44.0

[dependabot]

Bumps github.com/onsi/gomega from 1.43.1 to 1.44.0.

Release notes

Sourced from github.com/onsi/gomega's releases.

v1.44.0

Fixes

• BeNumerically compares signed and unsigned integers by value: -1 no longer equals uint64(math.MaxUint64) and uint(5) is now greater than -3 (#925) [26e3c6b]
• BeNumerically("~") no longer overflows when computing the distance between extreme integers (#928) [1955764]
• BeNumerically("==", x, threshold) now honors the threshold for floats, as it already did for integers (#927) [10e2aca]
• HaveKeyWithValue succeeds if any key accepted by the key matcher has a matching value, rather than depending on map iteration order (#929) [ffc577a]
• HaveKey and HaveKeyWithValue treat key and value matcher errors like ContainElement does: a match wins, and an error is only reported when nothing matches (#926) [dc91598]
• MatchJSON no longer treats numbers too large for a float64 as equal to one another (#930) [9d619a5]
• MatchJSON compares integers beyond ±2^53 exactly, so neighboring large integers (e.g. IDs) no longer match; all other numbers are still compared as float64s (#931) [8ef1aa7, 630fe12]
• HaveExactElements reports missing or extra elements that start at index 0, and reports the first extra element's index rather than the last (#934) [af1b777]
• MatchYAML compares every document in a multi-document stream rather than only the first; empty documents (e.g. a leading or trailing ---) are ignored (#933) [2773796]
• MatchXML ignores namespace prefixes: elements and attributes are compared by namespace URI, and the URIs declared on each element must match whatever prefix they are bound to (#932) [c0dbd89, 2565350]

Changelog

Sourced from github.com/onsi/gomega's changelog.

1.44.0

Fixes

• BeNumerically compares signed and unsigned integers by value: -1 no longer equals uint64(math.MaxUint64) and uint(5) is now greater than -3 (#925) [26e3c6b]
• BeNumerically("~") no longer overflows when computing the distance between extreme integers (#928) [1955764]
• BeNumerically("==", x, threshold) now honors the threshold for floats, as it already did for integers (#927) [10e2aca]
• HaveKeyWithValue succeeds if any key accepted by the key matcher has a matching value, rather than depending on map iteration order (#929) [ffc577a]
• HaveKey and HaveKeyWithValue treat key and value matcher errors like ContainElement does: a match wins, and an error is only reported when nothing matches (#926) [dc91598]
• MatchJSON no longer treats numbers too large for a float64 as equal to one another (#930) [9d619a5]
• MatchJSON compares integers beyond ±2^53 exactly, so neighboring large integers (e.g. IDs) no longer match; all other numbers are still compared as float64s (#931) [8ef1aa7, 630fe12]
• HaveExactElements reports missing or extra elements that start at index 0, and reports the first extra element's index rather than the last (#934) [af1b777]
• MatchYAML compares every document in a multi-document stream rather than only the first; empty documents (e.g. a leading or trailing ---) are ignored (#933) [2773796]
• MatchXML ignores namespace prefixes: elements and attributes are compared by namespace URI, and the URIs declared on each element must match whatever prefix they are bound to (#932) [c0dbd89, 2565350]

Commits

• c933817 v1.44.0
• 37fa900 v1.44.0 (full)
• 509f2b0 changelog: entries for fix(e2e): Add a step to check all containers are ready #925-#934
• 2565350 fix: MatchXML compares namespace declarations by URI, ignoring the prefix
• 630fe12 fix: MatchJSON only compares integers beyond 2^53 exactly
• c0dbd89 fix: MatchXML ignores namespace prefixes and declarations
• 2773796 fix: MatchYAML compares every document in a multi-document stream
• af1b777 fix: HaveExactElements reports missing/extra elements starting at index 0
• 8ef1aa7 fix: MatchJSON compares numbers exactly
• 9d619a5 fix: MatchJSON reports numbers that do not fit in a float64
• 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 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)