bump pinned ginkgo to v2.9.5

[longwuyuan]

What this PR does / why we need it:

• There are 4 places in the code where ginkgo version is pinned
• Dependabot bumped ginkgo from v2.9.0 to v2.9.5 in Bump github.com/onsi/ginkgo/v2 from 2.9.0 to 2.9.5 #9980
• Dependabot can/does not change the pinned version of ginkgo
• This PR is yet another one in a series of PRs that bumps pinned ginkgo version, whenever dependabot bumps ginkgo
• This PR will re-generate the test-runner docker image so follow up PRs should/will be created to promote the new test-runner image to prod registry, in addition to updating project code to use the newly promoted test-runner image tag and sha

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

• No issue was created as this is a follow up version upgrade

How Has This Been Tested?

• Can be tested in CI only after merging this and promoting the resulting new test-runner image

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added unit and/or e2e tests to cover my changes.
• All new and existing tests passed.

/triage accepted
/priority important-soon
/kind bug

cc @rikatz @cpanato @strongjz @tao12345666333 seeking review/lgtm/approve. thanks

[cpanato]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, longwuyuan

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:

• OWNERS [cpanato]

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