fix: remove codeowners

[hstove-stacks]

The CODEOWNERS file is great in concept, but it has a big downside of automatically adding a ton of people as reviewers to a PR. This is theoretically fine, but there is no way to filter Github notifications for PRs where you're explicitly tagged as a reviewer. Additionally, it means you're default "participating" in each PR, further hurting notification triage-ability.

[wileyj]

lgtm

[wileyj]

The CODEOWNERS file is great in concept, but it has a big downside of automatically adding a ton of people as reviewers to a PR. This is theoretically fine, but there is no way to filter Github notifications for PRs where you're explicitly tagged as a reviewer. Additionally, it means you're default "participating" in each PR, further hurting notification triage-ability.

all fair points - it's definitely outlived it's usefulness. kill it

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.47%. Comparing base (77f1583) to head (59705dd).
⚠️ Report is 2 commits behind head on develop.

❌ Your project status has failed because the head coverage (75.47%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #6714      +/-   ##
===========================================
- Coverage    75.65%   75.47%   -0.19%     
===========================================
  Files          577      577              
  Lines       357690   357690              
===========================================
- Hits        270624   269977     -647     
- Misses       87066    87713     +647     

see 79 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 77f1583...59705dd. Read the comment docs.

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