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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
github.com/onsi/ginkgo/v2	require	patch	v2.8.0 -> v2.8.1	v2.8.3 (+1)

---

Release Notes

onsi/ginkgo

v2.8.1

Compare Source

2.8.1

Fixes

• lock around default report output to avoid triggering the race detector when calling By from goroutines [2d5075a]
• don't run ReportEntries through sprintf [febbe38]

Maintenance

• Bump golang.org/x/tools from 0.5.0 to 0.6.0 (#​1135) [11a4860]
• test: update matrix for Go 1.20 (#​1130) [4890a62]
• Bump golang.org/x/sys from 0.4.0 to 0.5.0 (#​1133) [a774638]
• Bump github.com/onsi/gomega from 1.25.0 to 1.26.0 (#​1120) [3f233bd]
• Bump github-pages from 227 to 228 in /docs (#​1131) [f9b8649]
• Bump activesupport from 6.0.6 to 6.0.6.1 in /docs (#​1127) [6f8c042]
• Update index.md with instructions on how to upgrade Ginkgo [833a75e]

---

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.1 && 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 #867 (7e7ac6a) into main (9c813ac) will increase coverage by 0.07%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #867      +/-   ##
==========================================
+ Coverage   58.52%   58.60%   +0.07%     
==========================================
  Files          97       97              
  Lines        7552     7552              
==========================================
+ Hits         4420     4426       +6     
+ Misses       2939     2935       -4     
+ Partials      193      191       -2     

Impacted Files	Coverage Δ
...lers/lifecycle/keptnworkloadinstance/controller.go	82.95% <0.00%> (+1.34%)	⬆️
...ptnworkloadinstance/reconcile_prepostevaluation.go	90.90% <0.00%> (+9.09%)	⬆️

Flag	Coverage Δ
component-tests	42.20% <ø> (+0.54%)	⬆️
keptn-lifecycle-operator	54.67% <ø> (ø)
klt-cert-manager	67.50% <ø> (ø)
scheduler	21.17% <ø> (ø)

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.