[codex] rename chat connector bridge contracts

[numnx]

What changed

• Renamed Settings -> Integrations chat grouping to CHAT CONNECTORS and updated connector detail headings.
• Removed all legacy third-party bridge naming from source, dashboard copy, docs, and tests.
• Renamed chat connector bridge contract values to Code UX-owned terms: managed_bridge, managed_core, managed_plugin, bridgeApiKey, and bridgeUrl.
• Updated backend routing/security, MCP schemas, dashboard view models, tests, and canonical/public docs to match the new terminology.

Why

The chat connector implementation should not expose a third-party project name in product copy or internal contracts. This keeps the feature clearly owned by Code UX and avoids implying bundled or copied third-party code.

Copy audit notice

I checked the public repository at github.com/openclaw/openclaw by cloning it shallowly outside the workspace and running targeted searches for Code UX connector class names, table names, MCP tool names, headers, and distinctive routing/error strings. I also ran a local duplicate block scan comparing 2,033 non-trivial Code UX connector code blocks against that clone. I found no matching source symbols or copied code blocks.

Validation

• rg -ni "openclaw|open claw" . --glob '!node_modules/**' --glob '!.git/**' --glob '!dist/**' --glob '!dashboard/dist/**'
• pnpm vitest run tests/backend/server/chat-provider-routes.test.ts tests/backend/server/chat-provider-ingress-routes.test.ts tests/backend/services/chat-provider-ingress-service.test.ts tests/backend/services/chat-provider-outbound-service.test.ts tests/backend/mcp/management-chat-provider-actions.test.ts tests/dashboard/lib/chat-provider-view-models.test.ts tests/dashboard/lib/settings-search-index.test.ts tests/dashboard/v2/settings-chat-providers-panel.test.tsx
• pnpm run lint
• pnpm run build

Note: pnpm run build passed but still printed the existing node:net Vite warning from src/mcp/mcp-tool-availability.ts because this branch is based on dev; that warning is addressed in the separate MCP attachment PR.

Risk / rollback

No migrations were added because this chat connector release has not shipped. Roll back this commit to restore the previous contract names if needed before release.