Move view metadata (including view type) outside the configuration panel

[conservationtimothy]

Goal

Make immutable view identity (type, name, primary/secondary datasets) visible as read-only page metadata on /config/[dataset], instead of burying view type inside a collapsible “Views” section that looks configurable. Closes #501

Screenshots

What I changed and why

• Moved view type out of the editable ConfigCard form and into a read-only metadata block under the page header, making it clear that view type is fixed after creation
• Metadata block displays view type (icon + localized label), display name (viewName), primary dataset, and secondary dataset (or "None")
• Name and description remain editable inside ConfigCard as before; the metadata block only mirrors saved identity fields and refreshes the display name after a successful save
• Deleted ConfigViews.vue since the Views collapsible section is no longer needed
• Updated e2e expectations to assert the header metadata block instead of the Views collapsible
• Added i18n keys for the new metadata labels across all six locales

How I convinced myself this is right

The page already had the resolved view row (including viewName and secondaryDataset); the metadata block reads those values and keeps the same config-view-type-display test id so the type badge stays findable.

What I'm not doing here

• Search / view-type filter on /config (Add search and view type filter to config page #500)
• Type-first create flow (/config/new, Replace dataset-centric view creation workflow #499 )
• Changing primary/secondary semantics or edit route shape

LLM use disclosure

Cursor Grok 4.5 helped with translations

[rudokemper]

Thanks @conservationtimothy, before doing code review I checked out the UI in development and had some thoughts:

(1) can be the Dataset Display Name (e.g. "BCM Form Responses - Gallery" in this example) instead of the primary dataset repeated
(2) In that case, we don't need this "Name" metadata field
(3) Instead of repeating the primary dataset here, can we provide a friendly name like "Configuration Options" (localized)?
(4) Kind-of out of scope, but I wouldn't mind you fixing this here: Can the copy instead say "Copy Config from Another View"

Lastly, can the page title be GuardianConnector Explorer: Configuration - {dataset_name} instead of GuardianConnector Explorer: Configuration - {primary-dataset}?

[conservationtimothy]

@rudokemper , sure ! But hold off on code review till I've implemented your suggestions.

On 1 and 5: Yes but will fallback to primary dataset if no display name has been configured.

Everything else i agree with.