Add RunningHub channel integration (task adaptor, controller endpoints, and UI support)

[lwb8832652]

Motivation

• Integrate RunningHub as a new channel so the gateway can submit tasks, fetch public models, query account info and AI-app endpoints from RunningHub.
• Provide a task adaptor to map unified gateway task requests to RunningHub's openapi paths and normalize task responses and statuses.
• Expose admin routes and UI entries so channels and model lists for RunningHub can be managed from the dashboard.

Description

• Add ChannelTypeRunningHub (58) and its base URL and name in constant/channel.go, and map it to APITypeOpenAI in common/api_type.go for API-type fallback.
• Implement a RunningHub task adaptor (relay/channel/task/runninghub/adaptor.go) that builds RunningHub URLs, headers and bodies, handles submitting tasks, polling (/openapi/v2/query) and parsing task results and statuses, and marks RunningHub as stream-capable in relay/common/relay_info.go.
• Add controller support in controller/channel.go for fetching RunningHub models and several admin endpoints (ai_app/run, ai_app/demo, public_models, account/info, account/api_keys, account/queue_status) with helper request functions and doRunningHubRequest helper.
• Register the RunningHub task adaptor in relay/relay_adaptor.go and add new API routes in router/api-router.go with RootAuth protection, and expose RunningHub in frontend constants and icon mapping (web/src/constants/channel.constants.js, web/src/helpers/render.jsx).
• Add documentation docs/runninghub/INTERFACE_CATALOG.md describing mapped endpoints, conventions and recommended gateway mappings.

Testing

• Built the Go backend with go build ./... to ensure the new packages and imports compile successfully (build succeeded).
• Built the frontend assets with the project build command (npm run build / yarn build) to verify UI constants and icons compile into the bundle (build succeeded).
• No automated unit tests were added or modified in this change.

---

Codex Task

[lwb8832652]

ok