Show parameter display names instead of keys across schema forms, run results, and explorer details

[Irozuku]

Summary

Parameter labels in the frontend now show a single human readable display name instead of both the display name and the raw key. The schema field card, the run results parameter table, and the explorer details parameters tab all resolve each parameter's display name from schema data that is already loaded, so no extra backend calls are made.

---

Type of Change

• Backend change
• Frontend change
• CI / Workflow change
• Build / Packaging change
• Bug fix
• Documentation

---

Changes (by file)

• DashAI/front/src/components/shared/FormSchemaFieldCard.jsx: Header now renders only label ?? paramKey (display name, falling back to the key). Removed the separate monospace key line so each schema field shows one label.
• DashAI/front/src/components/models/RunCard.jsx: Pass the matched model (already resolved from the right side bar list) down to RunResults.
• DashAI/front/src/components/models/RunResults.jsx: Accept the model prop and map each run parameter key to its display name via model.schema.properties[key].title, falling back to the key. No extra fetch.
• DashAI/front/src/components/notebooks/explorer/ExplorerDetailsModal.jsx: Pass explorerComponent.schema into the parameters tab.
• DashAI/front/src/components/notebooks/explorer/tabs/Parameters.jsx: Accept a schema prop and resolve each parameter's display name from schema.properties[key].title, falling back to the key.

---

Testing

• Open any step that configures a component through a schema form (e.g. adding/configuring a model, converter, or explorer) and confirm each parameter shows a single title, not both the display name and the raw key.
• Open a run's model parameters table and confirm parameter rows show display names, not raw keys.
• Open an explorer's details > parameters tab and confirm the same.
• Confirm fallback to the raw key when a parameter has no display name in the schema.