chore: update CODEOWNERS with new team names

[jristau1984]

Continuing maintainership updates for 2U 2024.

Description

Describe what this pull request changes, and why. Include implications for people using this change.
Design decisions and their rationales should be documented in the repo (docstring / ADR), per
OEP-19, and can be
linked here.

Useful information to include:

• Which edX user roles will this change impact? Common user roles are "Learner", "Course Author",
  "Developer", and "Operator".
• Include screenshots for changes to the UI (ideally, both "before" and "after" screenshots, if applicable).
• Provide links to the description of corresponding configuration changes. Remember to correctly annotate these
  changes.

Supporting information

Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.

Testing instructions

Please provide detailed step-by-step instructions for testing this change.

Deadline

"None" if there's no rush, or provide a specific date or event (and reason) if there is one.

Other information

Include anything else that will help reviewers and consumers understand the change.

• Does this change depend on other changes elsewhere?
• Any special concerns or limitations? For example: deprecations, migrations, security, or accessibility.
• If your database migration can't be rolled back easily.

[jristau1984]

@kdmccormick this change requires adding write access to two new teams into edx-platform. Is this something you can do within the scope of this ticket, or do I need to file an Axim Engineering issue for it?

[kdmccormick]

@feanil , the error here states that 2u-tnl needs write access. Right now they have read access on the repo. When I bump the access level up to "write", the error here goes away.

[feanil]

Ah, Kyle, I misunderstood your question, I thought it was about adding people as reviewers and not for adding them as CODEOWNERS. Yes, you're right they do need write access and I think it's fine to add them explicitly to the list of collaborators for edx-platform.

[kdmccormick]

Thanks Jeremy!

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.