feat(providers): add Devin CLI and Devin Cloud as first-party providers - #7531

💭 I'm reviewing the changed web files, including icons, provider settings, composer draft store, context window logic, and session logic, to check consistency across the codebase—starting with how Icons.tsx compares to other icon implementations. The DevinIcon matches the pattern used by CursorIcon and GrokIcon, which is good. Now I want to check the session-logic PROVIDER_OPTIONS where devin and devinCloud were added with a "new" sidebar badge, and verify whether other places like a provider-order list or settings need corresponding entries. I should check providerDriverMeta.ts and ProviderModelsSection.tsx next, then look for other places in apps/web/src where providers are enumerated but Devin might be missing, like accent colors, settings sections, or the model picker sidebar. I'll grep for "grok" to find enumerations that may need Devin added for consistency. I should also check for provider accent color mapping or provider-specific classes in the web app, so I'll search for "grok" references outside test files to find where these lists are defined. Everything else checks out. I want to verify providerDriverMeta.ts and ProviderModelsSection to confirm the missing placeholder for devinCloud isn't a real issue—it likely just falls back to the default placeholder since that's driven by customModels presence, so it's a minor gap rather than a UI consistency violation. The web changes look consistent, with DevinIcon matching the CursorIcon/GrokIcon pattern exactly, including the fill approach. The apiKey password control is part of contracts and out of scope here, so now I want to check if there's a provider color map in the web code that lists providers by accent color. I notice the formatProcessType regex doesn't include devin, but that's pre-existing and not a UI-consistency issue this PR touches. Adding the Devin provider means devin processes will show as "Process" instead of "Agent" — arguably relevant but more of a labeling nit than a styling consistency concern, so it's borderline whether to flag it. Checking the web diff more carefully: Icons.tsx, providerIconUtils.ts, ProviderModelsSection.tsx, providerDriverMeta.ts, composerDraftStore.ts, contextWindow.ts, session-logic.ts — no CSS changes, no new component primitives. DevinIcon is placed alphabetically between CursorIcon and GrokIcon, which is consistent with convention. I'm also noting that providerDriverMeta gives an "Early Access" badge to Cursor and Grok since those drivers are off by default, and Devin/Devin Cloud appear to be off by default too, so I should check whether they're missing that same badge treatment for consistency.