No more mass pings due to the wrong base branch [skip treewide]

[infinisil]

This is an intentional final mass ping to make a PSA to everybody who's been plagued by unnecessary mass pings for all these years, because it won't happen any longer!

This is because since recently, we're not using the GitHub-native CODEOWNERS file, but rather the custom ci/OWNERS and a smart GitHub Action workflow to check it and request reviews based on it, with the major benefits of:

• When the wrong base branch is chosen, no mass ping is triggered, instead a helpful message (and only if the user doesn't immediately fix it)
• Code owners don't need to have write access

Please spread the news that we can freely set and change the base branch now without worrying about filling up notification inboxes, and encourage more people to add themselves as code owners 🚀

And if you spot any issues, let me know, I'll be tending to it

---

Original description:

Add support for Windows by changing all files to use CRLF as the file ending. Who knew it would be this simple!

---

This was sponsored by Antithesis and Tweag! ✨

[nix-owners]

The PR's base branch is set to master, but 1108 commits from the staging branch are included. Make sure you know the right base branch for your changes, then:

• If the changes should go to the staging branch, change the base branch to staging
• If the changes should go to the master branch, rebase your PR onto the merge base with the master branch:

  # git rebase --onto $(git merge-base upstream/master HEAD) $(git merge-base upstream/staging HEAD)
  git rebase --onto 9ee9cac8884ba11650ef6946a1bed9c7171f560a e694240f776e555ab4b0e3bab12dca20da7a9546
  git push --force-with-lease

[Frontear]

LGTM

[Frontear]

On a serious note, awesome to see it worked!

[emilazy]

Please fix the nixpkgs-vet error. Otherwise LGTM.

[AndersonTorres]

LGTM (looks gore to me)

[nix-owners]

The PR's base branch is set to staging, but 15 commits from the master branch are included. Make sure you know the right base branch for your changes, then:

• If the changes should go to the master branch, change the base branch to master
• If the changes should go to the staging branch, rebase your PR onto the merge base with the staging branch:

  # git rebase --onto $(git merge-base upstream/staging HEAD) $(git merge-base upstream/master HEAD)
  git rebase --onto b418f9bd8a04782f6614be88ce931bc3c2bf97c8 bb752745b2f44ebe6a70d5494af3101c739b3811
  git push --force-with-lease

[infinisil]

Turns out it's not possible to request more than 15 people with normal means, so it's very much impossible to mass ping people now! This isn't great though, it's fair to mass ping if the relevant files are changed legitimately, so I'll look into how this can be addressed. To avoid further notifications, let's close and lock this now though