chore: Add entire team as code owners for the changelog and Cargo.lock

[netrome]

Because virtually every PR may change these, and anyone in the team should be able to vet changes to these files.

[AurelienFT]

Of we do that I believe we will all be codeowners on all PRs and our approval will count as a code owner approval on the whole code just because the Changelog has been touched. Is it something we want ?

[netrome]

Of we do that I believe we will all be codeowners on all PRs and our approval will count as a code owner approval on the whole code just because the Changelog has been touched. Is it something we want ?

Nope that's not how code owners work. For each file with a code owner touched by a PR, you need an approval from a code owner of that file. This is how it's said in the docs:

Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch.

See: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-pull-request-reviews-before-merging

Also see this PR: #2598
I have codeowner approval for all fraud proof stuff, but it still requires approval from one of the oldies because of the changelog and Cargo.lock.

Appreciate the pushback, but the request is based on incorrect assumptions.

[AurelienFT]

Ok I believe you then, my bad. I just saw that when you look at files changed it says that "@acerone" doesn't exist I believe it should be "@acerone85"

[netrome]

Ok I believe you then, my bad. I just saw that when you look at files changed it says that "@acerone" doesn't exist I believe it should be "@acerone85"

Oh thanks for spotting, fixed now 🙏

Addressed the requested change.