[KEP-1933] Correct stable version to 1.23, not 1.22

[PurelyApplied]

• One-line PR description: Correct stable version to 1.23, not 1.22.

• Issue link: Defend against logging secrets via static analysis #1933

• Other comments: This change comes at the recommendation of @gracenng as 1.23 enhancement shadow. Since we recently merged the "official" stable state in the KEP's YAML, it should be reflected in 1.23 for enhancement tracking, not back-dating 1.22 of when scanning became blocking.
• Also, I noticed I left a trailing, empty comment line. Trimmed that form the YAML.

/sig security
/cc gracenng

[PurelyApplied]

Hmm, misunderstood how the bot autopopulates fields... Pulling cc and assign from recent #2847.

/cc tabbysable IanColdwater
/assign ehashman

[ehashman]

/lgtm

I was gonna ask about that :)

[deads2k]

/approve

[tabbysable]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, PurelyApplied, tabbysable

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:

• keps/prod-readiness/OWNERS [deads2k]
• keps/sig-security/OWNERS [tabbysable]

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