Add CODEOWNERS file for repo

[tcarmet]

made with @nicolas2bert as a example/test/showcase.

[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]

Missing Jira issue

It is mandatory to specify a Jira issue in the source branch name
in order to merge into development/9.1. The issue key must follow
the prefix of the branch.

I could not find such an issue in feature/add-codeowners.

[tcarmet]

/bypass_jira_check

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.89%. Comparing base (07cff46) to head (53ef27a).

Additional details and impacted files

see 4 files with indirect coverage changes

Components	Coverage Δ
Bucket Notification	80.36% <ø> (ø)
Core Library	81.12% <ø> (-0.04%)	⬇️
Ingestion	70.78% <ø> (ø)
Lifecycle	78.35% <ø> (ø)
Oplog Populator	85.06% <ø> (ø)
Replication	61.18% <ø> (+0.03%)	⬆️
Bucket Scanner	85.60% <ø> (ø)

@@                 Coverage Diff                 @@
##           development/9.1    #2675      +/-   ##
===================================================
- Coverage            74.90%   74.89%   -0.01%     
===================================================
  Files                  201      201              
  Lines                13577    13577              
===================================================
- Hits                 10170    10169       -1     
- Misses                3397     3398       +1     
  Partials                10       10              

Flag	Coverage Δ
api:retry	9.49% <ø> (ø)
api:routes	9.30% <ø> (ø)
bucket-scanner	85.60% <ø> (ø)
ft_test:queuepopulator	10.33% <ø> (-0.55%)	⬇️
ingestion	12.61% <ø> (ø)
lib	7.79% <ø> (+<0.01%)	⬆️
lifecycle	18.94% <ø> (+<0.01%)	⬆️
notification	1.03% <ø> (ø)
replication	18.80% <ø> (ø)
unit	50.72% <ø> (ø)

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.