Fix string output format for secret validations

[vivek-koppuru]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Continued from #103707, this aims to fix the error messaging that shows up for secret validations. Currently, the output is as follows when validation for basic auth secrets fail:

The Secret "secret-basic-auth" is invalid: 
* data[%s][username]: Required value
* data[%s][password]: Required value

With this PR, the output will be as follows:

The Secret "secret-basic-auth" is invalid: 
* data[username]: Required value
* data[password]: Required value

This will fix the format for the ssh auth secret as well.

Which issue(s) this PR fixes:

Fixes #

N/A

Special notes for your reviewer:

Let me know if I can do any other type of testing on my local machine apart from what is tested through Prow.

Does this PR introduce a user-facing change?

Not sure if this warrants a release note but it is as follows:

Fix bug in error messaging for basic-auth and ssh secret validations.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

@vivek-koppuru: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[k8s-ci-robot]

Hi @vivek-koppuru. Thanks for your PR.

I'm waiting for a kubernetes 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/test-infra repository.

[vivek-koppuru]

/sig auth

[vivek-koppuru]

@enj @liggitt What do you think, as we talked about this in a previous PR?

[liggitt]

/ok-to-test
/lgtm
/approve
/milestone v1.24

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, vivek-koppuru

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:

• pkg/apis/OWNERS [liggitt]

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

[vivek-koppuru]

Thanks for the approval @liggitt ! Since this is for milestone 1.24, this won't be merged until it is created for that based on the tide message? Will I need to keep track of this PR at a later time for potential merge conflicts?

[liggitt]

Since this is for milestone 1.24, this won't be merged until it is created for that based on the tide message?

This will merge once master reopens for 1.24 (in ~1 week).

Will I need to keep track of this PR at a later time for potential merge conflicts?

I wouldn't expect anything to touch this file between now and master reopening, but yeah, if there's a merge conflict, it'll need rebasing