ginkgo-linter: use Equal with different types: Comparing uint64 with int; either change the expected value type if possible, or use the BeEquivalentTo() matcher, instead of Equal()

ginkgo-linter: multiple issues: timeout defined more than once; polling defined more than once

ginkgo-linter: multiple issues: only use time.Duration for timeout and polling in Eventually() or Consistently(); only use time.Duration for timeout and polling in Eventually() or Consistently(). Consider using `Consistently(func() bool { return true }, time.Second*10, time.Second).Should(BeTrue())` instead

ginkgo-linter: timeout must not be shorter than the polling interval

ginkgo-linter: use a function call in Eventually. This actually checks nothing, because Eventually receives the function returned value, instead of function itself, and this value is never changed. Consider using `Eventually(withoutArguments).Should(Equal(42))` instead

ginkgo-linter: use a function call in Eventually. This actually checks nothing, because Eventually receives the function returned value, instead of function itself, and this value is never changed. Consider using `Eventually(withArguments).WithArguments(4, 2).Should(Equal(42))` instead

ginkgo-linter: use a function call in Eventually. This actually checks nothing, because Eventually receives the function returned value, instead of function itself, and this value is never changed. Consider using `Eventually(withArguments).WithArguments(4, 2).Should(Equal(42))` instead

ginkgo-linter: use a function call in Eventually. This actually checks nothing, because Eventually receives the function returned value, instead of function itself, and this value is never changed. Consider using `Eventually(withoutArguments).Should(Equal(42))` instead

ginkgo-linter: Success matcher only support a single error value, or function with Gomega as its first parameter

ginkgo-linter: wrong error assertion. Consider using `Eventually(func() error { return err }).Should(Succeed())` instead

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636