deps: update module github.com/onsi/ginkgo/v2 to v2.7.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
github.com/onsi/ginkgo/v2	require	patch	v2.7.0 -> v2.7.1

---

Release Notes

onsi/ginkgo

v2.7.1

Compare Source

2.7.1

Fixes

• Bring back SuiteConfig.EmitSpecProgress to avoid compilation issue for consumers that set it manually [d2a1cb0]

Maintenance

• Bump github.com/onsi/gomega from 1.24.2 to 1.25.0 (#​1118) [cafece6]
• Bump golang.org/x/tools from 0.4.0 to 0.5.0 (#​1111) [eda66c2]
• Bump golang.org/x/sys from 0.3.0 to 0.4.0 (#​1112) [ac5ccaa]
• Bump github.com/onsi/gomega from 1.24.1 to 1.24.2 (#​1097) [eee6480]

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: scheduler/go.sum

Command failed: docker run --rm --name=renovate_sidecar --label=renovate_child -v "/mnt/renovate/gh/keptn/lifecycle-toolkit":"/mnt/renovate/gh/keptn/lifecycle-toolkit" -v "/tmp/renovate-cache":"/tmp/renovate-cache" -v "/tmp/containerbase":"/tmp/containerbase" -e GOPATH -e GOPROXY -e GOFLAGS -e CGO_ENABLED -e GIT_CONFIG_KEY_0 -e GIT_CONFIG_VALUE_0 -e GIT_CONFIG_KEY_1 -e GIT_CONFIG_VALUE_1 -e GIT_CONFIG_KEY_2 -e GIT_CONFIG_VALUE_2 -e GIT_CONFIG_COUNT -e BUILDPACK_CACHE_DIR -e CONTAINERBASE_CACHE_DIR -w "/mnt/renovate/gh/keptn/lifecycle-toolkit/scheduler" docker.io/renovate/sidecar bash -l -c "install-tool golang 1.20.0 && go get -d -t ./... && go mod tidy && go mod tidy"
go: k8s.io/kube-scheduler@v0.0.0: reading k8s.io/kube-scheduler/go.mod at revision v0.0.0: unknown revision v0.0.0

[codecov]

Codecov Report

Merging #729 (e68f15a) into main (48b0dbc) will decrease coverage by 0.70%.
The diff coverage is n/a.

❗ Current head e68f15a differs from pull request most recent head abc2434. Consider uploading reports for the commit abc2434 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #729      +/-   ##
==========================================
- Coverage   57.69%   57.00%   -0.70%     
==========================================
  Files          91       83       -8     
  Lines        7243     6763     -480     
==========================================
- Hits         4179     3855     -324     
+ Misses       2894     2780     -114     
+ Partials      170      128      -42     

Impacted Files	Coverage Δ
...anager/controllers/keptnwebhookcontroller/certs.go
klt-cert-manager/kubeutils/secret.go
klt-cert-manager/kubeutils/certificates.go
klt-cert-manager/kubeutils/query.go
...rs/keptnwebhookcontroller/webhook_configuration.go
klt-cert-manager/eventfilter/eventfilter.go
...llers/keptnwebhookcontroller/certificate_secret.go
...okcontroller/keptnwebhookcertificate_controller.go

Flag	Coverage Δ
component-tests	47.93% <ø> (ø)
klt-cert-manager	?

Flags with carried forward coverage won't be shown. Click here to find out more.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.