feat(Catalog/PlatformCatalogSchemas): add Catalog Schemas platform entity with lossless SchemaGrid round-trip (Issue #4555)

[dearsimanovich-epam]

Description:

DIAL Core has carried a catalog_schemas resource type since 0.47.1 — a registered JSON-Schema document describing the display metadata a catalog entity type exposes — but the admin console had no surface for it, so the only way to register or edit one was a hand-written PUT against Core, with no validation (Core stores the body verbatim and checks nothing but the $id). This change adds the Catalog ▸ Catalog Schemas entity as a Core-direct CRUD surface following the same flat shape as the other seven Catalog entities, plus client-side meta-schema validation that substitutes for Core's absent write-time checks.

Fixing the shared SchemaGrid for catalog schemas also fixes it for App Runners: the grid reconstructed each property from a fixed field set, silently dropping format and dial:file and preserving dial:meta only on first-level properties. It is now a lossless round-trip, which is an observable behavior change to platform-app-runners and is specified as such. Deliberately out of scope (deferred): the config-file half of the population, and the consumer side that selects a schema and edits catalog_properties on models, applications, toolsets, skills and interceptors.

Issues:

• Issue Support Catalog Schemas as a new platform entity #4555

Key Changes:

• apps/ai-dial-admin/src/components/Assets/Platform/CatalogSchemas/ — the new entity's list, view, Properties/Parameters tabs and create flow, with specs
• apps/ai-dial-admin/src/app/[lang]/platform-catalog-schemas/ — list page, detail page and actions.ts
• apps/ai-dial-admin/src/components/Common/SchemaGrid/utils.ts — lossless round-trip: format, dial:file and nested dial:meta survive an edit
• apps/ai-dial-admin/src/components/Common/SchemaGrid/columns.tsx — optional catalog presentation-hint columns (dial:tab, dial:section, dial:widget, dial:localized)
• apps/ai-dial-admin/src/utils/core-schemas/resource-name.ts — $id-to-resource-name helpers extracted out of utils/app-runners/core-runner-name.ts so both entities share one implementation
• apps/ai-dial-admin/src/utils/catalog-schemas/validation.ts — client-side meta-schema validation blocking a save Core would accept but its config loader would reject
• apps/ai-dial-admin/src/constants/assets-core.ts, publications-core.ts, server/core/asset-metadata.ts — ResourceType.CATALOG_SCHEMA registered end-to-end
• openspec/specs/platform-catalog-schemas/spec.md and platform-app-runners/spec.md — synced main specs; the change is archived under openspec/changes/archive/2026-09-15-add-platform-catalog-schemas/

New Components:

• Assets/Platform/CatalogSchemas/{List,View,TabsContent,Properties,Parameters,CreateProperties} — the entity's list and two-tab detail surface
• context/assets/CatalogSchemasFolderContext.tsx — folder context for the new entity, matching the sibling Catalog entities
• utils/core-schemas/ — shared $id/resource-name module used by both App Runners and Catalog Schemas

Breaking Changes:

utils/app-runners/core-runner-name.ts is removed; its helpers now live in utils/core-schemas/resource-name.ts. All in-repo callers are updated in this change — no external consumers.

Checklist:

• the pull request name complies with Conventional Commits
• the pull request name ends with (Issue #4555) (comma-separated list of issues)

🤖 Generated with Claude Code