S3UTILS-214 improve codecov config and experience

[tcarmet]

Couple of things, we need to build on the default branch for codecov to have a base upon it will make comparisons when PRs are made.

Second is the condition upon codecov will send a check as a failure or not depending on how much coverage is added or removed on each new PR

[bert-e]

Hello tcarmet,

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]

Incorrect fix version

The Fix Version/s in issue S3UTILS-214 contains:

• None

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

• 1.18.0

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

[tcarmet]

/approve

[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: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/1

The following branches have NOT changed:

• development/1.13
• development/1.14
• development/1.15
• development/1.16
• development/1.17
• development/1.4
• development/1.7

Please check the status of the associated issue S3UTILS-214.

Goodbye tcarmet.

The following options are set: approve

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.62%. Comparing base (96e0a12) to head (2f30c6e).
⚠️ Report is 2 commits behind head on development/1.

Additional details and impacted files

@@              Coverage Diff               @@
##           development/1     #373   +/-   ##
==============================================
  Coverage          43.62%   43.62%           
==============================================
  Files                 84       84           
  Lines               5973     5973           
  Branches            1255     1255           
==============================================
  Hits                2606     2606           
  Misses              3321     3321           
  Partials              46       46           

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

🚀 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.