Update ml codeowners

[diondrapeck]

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[needuv]

Given that the SDK has largely been centralized to Nupur's team, can we simplify the ML code paths? It was so split up due to many different teams owning the SDK

[diondrapeck]

Given that the SDK has largely been centralized to Nupur's team, can we simplify the ML code paths? It was so split up due to many different teams owning the SDK

Fair point - will do!