[chore] Run make genotelcorecol to fix "build-and-test / checks"

[jade-guiton-dd]

Description

The "build-and-test / checks" CI job specifies go-version: ~1.22.8. Today, this started resolving to 1.22.9, causing errors in CI because of the toolchain 1.22.8 directive in otelcorecol/go.mod. This PR just updates the directive to fix the error. A more long-term solution may be preferred, such as using exact versions instead of ~ versions in CI.

[bogdandrutu]

You need to update https://github.com/open-telemetry/opentelemetry-collector/blob/main/.github/workflows/build-and-test.yml#L48 (and everywhere)

[jade-guiton-dd]

Interesting, at the moment it seems some runs of check resolve ~1.22.8 to 1.22.8, and others to 1.22.9...

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.64%. Comparing base (eaeacaf) to head (c7c7146).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11676      +/-   ##
==========================================
+ Coverage   91.62%   91.64%   +0.01%     
==========================================
  Files         439      442       +3     
  Lines       23682    23746      +64     
==========================================
+ Hits        21698    21761      +63     
- Misses       1615     1616       +1     
  Partials      369      369              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bogdandrutu]

Interesting, at the moment it seems some runs of check resolve ~1.22.8 to 1.22.8, and others to 1.22.9...

Can you clarify ?

[jade-guiton-dd]

Can you clarify ?

The failing run I linked earlier specified version ~1.22.8, which resolved to 1.22.9, causing a conflict with the toolchain 1.22.8 directive.

But the first run in this PR also failed, because the same specification resolved to 1.22.8, causing a conflict with the updated toolchain 1.22.9 directive. I suspect some kind of cache effect causing different runs to find different "latest" versions.

I just updated the CI to use ~1.22.9, so for the time being it should be unambiguous, but I think that's an additional reason to want to switch to exact minor versions.