Bump kafka_version from 3.6.1 to 3.7.0

[dependabot]

Bumps kafka_version from 3.6.1 to 3.7.0.
Updates org.apache.kafka:kafka-clients from 3.6.1 to 3.7.0

Updates org.apache.kafka:kafka_2.13 from 3.6.1 to 3.7.0

Updates org.apache.kafka:kafka-server-common from 3.6.1 to 3.7.0

Updates org.apache.kafka:kafka-group-coordinator from 3.6.1 to 3.7.0

Updates org.apache.kafka:kafka-metadata from 3.6.1 to 3.7.0

Updates org.apache.kafka:kafka-storage from 3.6.1 to 3.7.0

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[willyborankin]

there are breaking changes for Kafka. Not sure do we want to upgrade?

[peternied]

java.lang.ClassNotFoundException: org.apache.kafka.server.NodeToControllerChannelManager

Not sure its a breaking change, looks like there might be some test binaries that need to be incremented at the same time.

[cwperks]

I believe this can be resolved by adding testImplementation "org.apache.kafka:kafka-server:${kafka_version}" as a dependency. The org.apache.kafka.server.NodeToControllerChannelManager class was moved in this PR.

[cwperks]

I believe this can be resolved by adding testImplementation "org.apache.kafka:kafka-server:${kafka_version}" as a dependency. The org.apache.kafka.server.NodeToControllerChannelManager class was moved in this PR.

@peternied @willyborankin I pushed a commit to add this dependency to account for the missing class changing packages/jars.

[DarshitChanpura]

LGTM. We can always revert if its decided at some point that the blast radius is too big for this change.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.92%. Comparing base (f3b5727) to head (c73776d).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4087      +/-   ##
==========================================
+ Coverage   65.90%   65.92%   +0.02%     
==========================================
  Files         298      298              
  Lines       21352    21352              
  Branches     3475     3475              
==========================================
+ Hits        14071    14076       +5     
+ Misses       5541     5535       -6     
- Partials     1740     1741       +1     

see 1 file with indirect coverage changes

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/security/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/security/backport-2.x
# Create a new branch
git switch --create backport/backport-4087-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d235d97840a8450426f3c9d272e91f6afbd6ddce
# Push it to GitHub
git push --set-upstream origin backport/backport-4087-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/security/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-4087-to-2.x.