chore: bump github.com/oasdiff/oasdiff from 1.22.0 to 1.23.0 in /tools/cli

[dependabot]

Justification for changes:

• specInfoPair was only ever used to feed two version strings (Base.Version, Revision.Version) into RenderChangelog.
• In oasdiff 1.23.0, RenderChangelog no longer takes those strings — they moved onto just the HTML/Markup formatters, the only ones that render versions.
• This code uses the JSON formatter, which never rendered versions anyway, so passing them was already a no-op. Dropping them changes no output.

Bumps github.com/oasdiff/oasdiff from 1.22.0 to 1.23.0.

Release notes

Sourced from github.com/oasdiff/oasdiff's releases.

v1.23.0

Nullability changes recognized in every form, at every level

OpenAPI has three equivalent ways to make a schema nullable: the nullable keyword (3.0), a "null" entry in the type array (3.1), and wrapping the schema in oneOf: [{type: "null"}, X], the common idiom for $ref'd schemas. oasdiff now recognizes all three as one thing and reports a single became-nullable or became-not-nullable finding, in both directions, for bodies, properties, parameters, and parameter properties. The new nullability guide explains the model, when a nullability change is breaking, and the deliberate limits.

CLI changes

• Wrapping a schema in oneOf: [{type: "null"}, X] is one INFO finding, not false breaking errors (#1089, fixes #1088, thanks @​katepol for the report). The wrap moves the schema one level down, so the enum used to read as removed (two false request-property-enum-value-removed errors per wrapped enum), plus pattern-removed, one-of-added, and type-generalized noise. oasdiff now proves the wrapped branch is equivalent to the original and reports one became-nullable. The recognition declines conservatively when the edit is more than a pure wrap: an already-nullable schema, a branch that also changed (the constraint reports remain), or a null branch added to a multi-branch oneOf.
• Removing the wrapper is one became-not-nullable finding (#1092, fixes #1091). The reverse edit used to report echoes, including a false request-property-became-enum and a false new-required-request-property. On the request side this is an error (the request no longer accepts null); on the response side it is informational, via the new response-body-became-not-nullable and response-property-became-not-nullable verdicts, which also cover the keyword and type-array forms that previously reported nothing at all on responses.
• Parameters get nullability checks (#1093, fixes #1017). A query, path, or header parameter flipping between type: [string, "null"] and type: string was silent in both directions, although the removal direction is breaking. New verdicts: request-parameter-became-nullable (info), request-parameter-became-not-nullable (error), and the request-parameter-property-* pair for properties of object parameters. Response headers are not covered yet (#1094).
• Changelog output schema additions: six new rule ids (the response and parameter became-(not-)nullable families), localized in all four locales.

Go package changes

• Breaking: Formatter.RenderChangelog no longer takes version strings (#1085). Only the HTML and markup formatters render the base and revision versions, so the versions moved into those formatters' options and off the shared interface; the other six formatters no longer carry dead parameters.
• Breaking: ComputeFingerprint moved from formatters to checker (#1086). It computes a change's stable identity from checker.Change fields and has no formatting logic; callers that only need a fingerprint no longer depend on the output-rendering package. Call sites change from formatters.ComputeFingerprint to checker.ComputeFingerprint; output is byte-identical.
• New: ApiChange.WithSchema and the schema transitions table (#1089, #1092). Checkers no longer carry suppression code: a change built with WithSchema(node) is dropped automatically when a recognized schema transition at that node explains it (checker/transition_claims.go pairs each recognition with the finding kinds it claims and the rules that report it). diff.SchemaDiff gains NullableWrappingDiff.

Changelog

• 48c3e04facf8c4dba125e1f88a4212aed5c1c7bc docs: note the response-header limitation in NULLABILITY.md (#1094) (#1095)
• b3a525077668195639eb13726bef5c2d8646aae7 feat(checker): nullability checks for parameters (#1017) (#1093)
• 3433af958d2a9a38d53aa417911e640d1862faea fix: report nullability removal as became-not-nullable (#1091) (#1092)
• 1e3edff0df52c082c3328269373093cac03d6e11 fix(diff): recognize the nullable oneOf wrapping (#1088) (#1089)
• a5118c99b5b0616df92d5eb012fff578bb83357a chore: apply gopls modernize suggestions (#1087)
• 7663150a47216582b5db522d12fa1cd7bd382702 checker: move ComputeFingerprint out of formatters (#1086)
• 1bb851f9914044903b3dd96e4347570e0df4fc2c formatters: carry changelog versions only in HTML and Markup (#1085)

Commits

• 48c3e04 docs: note the response-header limitation in NULLABILITY.md (#1094) (#1095)
• b3a5250 feat(checker): nullability checks for parameters (#1017) (#1093)
• 3433af9 fix: report nullability removal as became-not-nullable (#1091) (#1092)
• 1e3edff fix(diff): recognize the nullable oneOf wrapping (#1088) (#1089)
• a5118c9 chore: apply gopls modernize suggestions (#1087)
• 7663150 checker: move ComputeFingerprint out of formatters (#1086)
• 1bb851f formatters: carry changelog versions only in HTML and Markup (#1085)
• See full diff in compare view

[yelizhenden-mdb]

@dependabot rebase

[yelizhenden-mdb]

@dependabot rebase