CLDSRV-1012: Bump arsenal for DataWrapper leak

[BourgoisMickael]

Close data stream on KMS error
Replace pipe with pipeline to propagate errors and premature close

[bert-e]

Hello bourgoismickael,

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	⭐
/bypass_source_branch_lineage	Bypass the cross-branch contamination check	⭐
/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 85.28%. Comparing base (654b065) to head (51c9c02).
⚠️ Report is 26 commits behind head on development/9.3.
✅ All tests successful. No failed tests found.

Additional details and impacted files

see 3 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.3    #6316      +/-   ##
===================================================
- Coverage            85.33%   85.28%   -0.06%     
===================================================
  Files                  206      206              
  Lines                13442    13442              
===================================================
- Hits                 11471    11464       -7     
- Misses                1971     1978       +7     

Flag	Coverage Δ
file-ft-tests	68.38% <ø> (+0.03%)	⬆️
file-ft-tests-null-compat	68.84% <ø> (ø)
kmip-ft-tests	28.35% <ø> (ø)
mongo-v0-ft-tests	69.60% <ø> (ø)
mongo-v1-ft-tests	69.52% <ø> (-0.10%)	⬇️
multiple-backend	36.80% <ø> (ø)
s3c-ft-tests-v0	63.98% <ø> (ø)
s3c-ft-tests-v0-null-compat	64.04% <ø> (ø)
s3c-ft-tests-v1	63.96% <ø> (ø)
sur-tests	35.94% <ø> (-0.03%)	⬇️
sur-tests-inflights	37.81% <ø> (+0.02%)	⬆️
unit	71.28% <ø> (ø)
utapi-v2-tests	34.60% <ø> (-0.03%)	⬇️

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

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bert-e]

Incorrect fix version

The Fix Version/s in issue CLDSRV-1012 contains:

• 7.10.61

• 7.70.78

• 8.8.60

• 9.0.38

• 9.1.16

• 9.2.43

• 9.3.23

• 9.4.8

• 9.5.0

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 9.3.23

• 9.4.8

• 9.5.0

Please check the Fix Version/s of CLDSRV-1012, or the target
branch of this pull request.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

[BourgoisMickael]

/create_integration_branches

[bert-e]

Conflict

A conflict has been raised during the creation of
integration branch w/9.4/improvement/CLDSRV-1012-bump-arsenal-datawrapper with contents from improvement/CLDSRV-1012-bump-arsenal-datawrapper
and development/9.4.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.4/improvement/CLDSRV-1012-bump-arsenal-datawrapper origin/development/9.4
 git merge origin/improvement/CLDSRV-1012-bump-arsenal-datawrapper
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.4/improvement/CLDSRV-1012-bump-arsenal-datawrapper

The following options are set: create_integration_branches

[bert-e]

Conflict

A conflict has been raised during the creation of
integration branch w/9.5/improvement/CLDSRV-1012-bump-arsenal-datawrapper with contents from w/9.4/improvement/CLDSRV-1012-bump-arsenal-datawrapper
and development/9.5.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.5/improvement/CLDSRV-1012-bump-arsenal-datawrapper origin/development/9.5
 git merge origin/w/9.4/improvement/CLDSRV-1012-bump-arsenal-datawrapper
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.5/improvement/CLDSRV-1012-bump-arsenal-datawrapper

The following options are set: create_integration_branches

[bert-e]

Waiting for approval

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

• the author

• 2 peers

The following options are set: create_integration_branches