CLDSRV-942: Fix missing s3 logs artifact for S3C

[BourgoisMickael]

• Fix missing s3 logs artifact for S3C
• Fix missing coverage for matrix job (s3c & file)

[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	⭐
/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 TBA
/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.

[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.3/bugfix/CLDSRV-942-s3-logs-coverage with contents from bugfix/CLDSRV-942-s3-logs-coverage
and development/9.3.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.3/bugfix/CLDSRV-942-s3-logs-coverage origin/development/9.3
 git merge origin/bugfix/CLDSRV-942-s3-logs-coverage
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.3/bugfix/CLDSRV-942-s3-logs-coverage

The following options are set: create_integration_branches

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.83%. Comparing base (7b2dbfb) to head (fec79cf).
✅ All tests successful. No failed tests found.

Additional details and impacted files

see 7 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.2    #6216      +/-   ##
===================================================
+ Coverage            84.50%   84.83%   +0.32%     
===================================================
  Files                  204      204              
  Lines                13217    13217              
===================================================
+ Hits                 11169    11212      +43     
+ Misses                2048     2005      -43     

Flag	Coverage Δ
file-ft-tests	68.17% <ø> (+0.05%)	⬆️
file-ft-tests-null-compat	68.63% <ø> (?)
kmip-ft-tests	28.41% <ø> (ø)
mongo-v0-ft-tests	69.35% <ø> (-0.06%)	⬇️
mongo-v1-ft-tests	69.35% <ø> (-0.06%)	⬇️
multiple-backend	35.68% <ø> (ø)
s3c-ft-tests-v0	63.49% <ø> (?)
s3c-ft-tests-v0-null-compat	63.56% <ø> (?)
s3c-ft-tests-v1	63.47% <ø> (?)
sur-tests	35.96% <ø> (-0.84%)	⬇️
sur-tests-inflights	37.83% <ø> (ø)
unit	70.34% <ø> (ø)
utapi-v2-tests	34.69% <ø> (ø)

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]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge bugfix/CLDSRV-942-s3-logs-coverage into
  development/9.2
• w/9.3/bugfix/CLDSRV-942-s3-logs-coverage will be merged into development/9.3
• w/9.4/bugfix/CLDSRV-942-s3-logs-coverage will be merged into development/9.4

The following branches will NOT be impacted:

• development/7.10
• development/7.4
• development/7.70
• development/8.8
• development/9.0
• development/9.1

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

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