Upgrade node-rdkafka to 3.6.1

[delthas]

Pin node-rdkafka to 3.6.1 exactly (librdkafka 2.12.0), replacing the 3.0.1 / librdkafka 2.3.0 from BB-806. S3C-11389 raises Federation's message-format pin, which removes the legacy v0/v1 MessageSet constraint that forced that downgrade.

Measured on CI over 25 runs per arm of the full lib suite: 20/25 jobs fail on librdkafka 2.3.0, and 0/25 on 2.12.0.

The pin stays exact rather than a caret — ^2.12.0 previously resolved forward from node-rdkafka 2.12.0 to 2.18.0, which changed the bundled librdkafka from 1.7.0 to 2.3.0 with no review.

Issue: BB-852

[bert-e]

Hello delthas,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request.
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.47%. Comparing base (52b9510) to head (3f74ba0).
⚠️ Report is 1 commits behind head on development/9.6.

Additional details and impacted files

see 3 files with indirect coverage changes

Components	Coverage Δ
Bucket Notification	80.27% <ø> (ø)
Core Library	81.23% <ø> (-0.71%)	⬇️
Ingestion	70.09% <ø> (ø)
Lifecycle	80.46% <ø> (ø)
Oplog Populator	85.83% <ø> (ø)
Replication	62.01% <ø> (ø)
Bucket Scanner	85.76% <ø> (ø)

@@                 Coverage Diff                 @@
##           development/9.6    #2817      +/-   ##
===================================================
- Coverage            75.76%   75.47%   -0.29%     
===================================================
  Files                  200      200              
  Lines                13922    13922              
===================================================
- Hits                 10548    10508      -40     
- Misses                3364     3404      +40     
  Partials                10       10              

Flag	Coverage Δ
api:retry	9.10% <ø> (ø)
api:routes	8.87% <ø> (ø)
bucket-scanner	85.76% <ø> (ø)
ft_test:queuepopulator	9.16% <ø> (-1.83%)	⬇️
ingestion	12.26% <ø> (ø)
lib	8.78% <ø> (-0.05%)	⬇️
lifecycle	19.28% <ø> (-0.03%)	⬇️
notification	1.02% <ø> (ø)
oplogPopulator	0.13% <ø> (ø)
replication	18.82% <ø> (-0.03%)	⬇️
unit	54.88% <ø> (ø)

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers