Route MiniMax-M3 and MiniMax-M2.7 to the OpenAI provider

[octo-patch]

Description

Add exact model-ID routing for MiniMax-M3 and MiniMax-M2.7 through the existing OpenAI-compatible provider. Both IDs now resolve to OpenAILanguageModel; the change does not add a new API client, protocol adapter, endpoint field, model metadata, or credential handling. Callers continue to provide their OpenAI-compatible base URL through the existing provider configuration.

The code change is limited to:

• langextract/providers/patterns.py: register the two exact model IDs.
• tests/registry_test.py: verify that both IDs resolve to the existing OpenAI provider.

This repository requires a linked issue with community discussion and at least five unique thumbs-up reactions. No qualifying issue is currently available for this change, so that repository policy remains outstanding.

How Has This Been Tested?

• python3 -m py_compile langextract/providers/patterns.py
• python3 -m py_compile tests/registry_test.py
• A dependency-free assertion that both exact model IDs match OPENAI_PATTERNS
• git diff HEAD^ HEAD --check
• GitHub Actions: format-check, test (3.10), test (3.11), test (3.12), plugin-integration-test, and ollama-integration-test

The targeted registry test could not start locally because the environment does not provide absl or pytest. It passed in the hosted Python jobs with project dependencies installed.

Checklist

• I have read the contribution guidelines and kept the change focused.
• The Google CLA check is passing.
• The change is linked to a qualifying issue with the required community support.
• No documentation changes are needed because the existing provider configuration remains unchanged.
• A focused registry test covers both model IDs.
• The changed Python files compile and the committed diff passes whitespace checks.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[github-actions]

No linked issues found. Please link an issue in your pull request description or title.

Per our Contributing Guidelines, all PRs must:

• Reference an issue with one of:
  • Closing keywords: Fixes #123, Closes #123, Resolves #123 (auto-closes on merge in the same repository)
  • Reference keywords: Related to #123, Refs #123, Part of #123, See #123 (links without closing)
• The linked issue should have 5+ 👍 reactions from unique users (excluding bots and the PR author)
• Include discussion demonstrating the importance of the change

You can also use cross-repo references like owner/repo#123 or full URLs.

[github-actions]

⚠️ Branch Update Required

Your branch is 1 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

[github-actions]

⚠️ Branch Update Required

Your branch is 7 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.