#20779: fix(providers): rename MiniMax M2.5 Lightning to M2.5 highspeed

## Summary - Problem: MiniMax has renamed the M2.5 Lightning model to M2.5 highspeed, but the codebase still references the old name. - Why it matters: Model IDs and display names should match the provider's official naming to avoid confusion. - What changed: Renamed all occurrences of `MiniMax-M2.5-Lightning` / `MiniMax M2.5 Lightning` to `MiniMax-M2.5-highspeed` / `MiniMax M2.5 highspeed` across model config, auth choice options, onboarding, and changelog. - What did NOT change (scope boundary): No logic changes; only string renames. The `minimax-api-lightning` auth choice value is kept as-is since it is a stable internal identifier. ## Change Type (select all) - [x] Bug fix - [ ] Feature - [ ] Refactor - [ ] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [ ] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [ ] Memory / storage - [x] Integrations - [ ] API / contracts - [x] UI / DX - [ ] CI/CD / infra ## Linked Issue/PR - Related #14865 ## User-visible / Behavior Changes - The MiniMax Lightning model option now displays as "MiniMax M2.5 highspeed" in onboarding and auth choice prompts. - The model ID sent to the MiniMax API changes from `MiniMax-M2.5-Lightning` to `MiniMax-M2.5-highspeed`. ## Security Impact (required) - New permissions/capabilities? No - Secrets/tokens handling changed? No - New/changed network calls? No - Command/tool execution surface changed? No - Data access scope changed? No ## Compatibility / Migration - Backward compatible? Yes - Config/env changes? No - Migration needed? No ## Risks and Mitigations - Risk: Users with existing config referencing the old `MiniMax-M2.5-Lightning` model ID may need to update their config. - Mitigation: This is a provider-driven rename; the old ID would stop working on MiniMax's side regardless. Made with [Cursor](https://cursor.com) <!-- greptile_comment --> <h3>Greptile Summary</h3> Renamed MiniMax M2.5 Lightning model to MiniMax M2.5 highspeed across model configurations, auth choice options, and onboarding flows to match MiniMax's official naming update. - Updated model ID from `MiniMax-M2.5-Lightning` to `MiniMax-M2.5-highspeed` in models config (`models-config.providers.ts:441-442`) - Updated display name from "MiniMax M2.5 Lightning" to "MiniMax M2.5 highspeed" in auth choice options (`auth-choice-options.ts:296`) - Updated model catalog entry in onboarding models (`onboard-auth.models.ts:85`) - Updated model ID mapping in auth choice handlers (`auth-choice.apply.minimax.ts:77`, `auth-choice.ts:587`) - Updated changelog reference to reflect the new naming (`CHANGELOG.md:626`) - The internal auth choice value `minimax-api-lightning` remains unchanged as a stable identifier <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk - This is a straightforward string rename that updates model IDs and display names to match MiniMax's official naming convention. All occurrences have been consistently updated across the codebase (model config, auth options, onboarding, changelog). No logic changes were made, only string replacements. The internal identifier `minimax-api-lightning` was correctly preserved as a stable internal value. - No files require special attention _{Last reviewed commit: c933ed1} <!-- greptile_other_comments_section --> _{(4/5) You can add custom instructions or style guidelines for the agent [here](https://app.greptile.com/review/github)!} <!-- /greptile_comment -->