fixed multiple ginkgo versions

[longwuyuan]

What this PR does / why we need it:

• ginkgo version was changed in /go.mod Bump github.com/onsi/ginkgo/v2 from 2.4.0 to 2.5.1 #9317
  , without changing the hardcoded ginkgo version in the project's scripts
• This PR tries to set the ginkgo version to v2.5.1, in the scripts/code, where ginkgo version is hardcoded, to be consistent with the change in /go.mod
• In future, we should use this PR to understand, what files & lines to edit, for bumping ginkgo version in the project
• This will create new test-runner image, that will need to be promoted asap, to make progress on make kind-e2e-test should generate junit reports #9321
• Discovered this while running make kind-e2e-test
• After this PR, there are ginkgo feature deprecations, that need to be addressed in a follow-up PR. Example

You're using deprecated Ginkgo functionality:             
=============================================             
  --ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose spe
cs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.
  --ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, inst
ead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.

To silence deprecations that can be silenced set the following environment variable:                                
  ACK_GINKGO_DEPRECATIONS=2.5.1  

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 created with direct reference but this is blocking make kind-e2e-test should generate junit reports #9321

How Has This Been Tested?

• Tested locally. Non-functional tests are running

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.
• Added Release Notes.

Does my pull request need a release note?

Any user-visible or operator-visible change qualifies for a release note. This could be a:

• CLI change
• API change
• UI change
• configuration schema change
• behavioral change
• change in non-functional attributes such as efficiency or availability, availability of a new platform
• a warning about a deprecation
• fix of a previous Known Issue
• fix of a vulnerability (CVE)

No release notes are required for changes to the following:

• Tests
• Build infrastructure
• Fixes for unreleased bugs

For more tips on writing good release notes, check out the Release Notes Handbook

fixed multiple ginkgo versions

/triage accepted
/area stabilization

/assign @rikatz @tao12345666333

[rikatz]

/lgtm
Thanks

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [rikatz]

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

[strongjz]

I hate our build sometimes, sorry @longwuyuan I blindly approved the dependabot pr.

[longwuyuan]

Aah, I got to learn tons and now I know what not to do. So thank you for being teacher/mentor yet again :-)

[longwuyuan]

/kind bug