support of distinct search-typename in WMS layers

[tha-nordiq]

Description

The search object is a reference to a corresponding WFS-service on a WMS layer.
It is used in various places like filters and attribute table.
At the moment the typename is assumed to be identical to the layer-name of the WMS.
this assumption is not always correct and so for some layers, having a corresponding wfs is impossible.
We lack a seperate typename in the searchObject.

Example

{
    "name": "pdk:theme_pdk_lokalplandelomraade_vedtaget",
    "type": "wms",
    "url": "https://geoserver1.plandata.dk/geoserver/wms",
    "search": {
        "url": "https://geoserver2.plandata.dk/geoserver/wfs",
        "type": "wfs",
        "typeName": "pdk:lokalplandelomraade"
    },
    ...
}

Acceptance criteria

• separate typename in layer.search.typeName
• used in every place the layers wfs is used
• gui to edit the url and typename

mockup

[tha-nordiq]

see also #12571

[offtherailz]

It's very useful to be able to change this data without edit JSON.
Agreed this needs its own typeName, the layer.name assumption breaks for cases like yours.

Since #12571 is narrowing down to just the layer's own URL, let's consolidate everything about the connected WFS service here:

• search.url, search.typeName (and maybe in the future version of WFS).

Because "search" is not IMHO semantically correct, In the UI I'd show:

"WFS linked service"

With the possibility to add/remove and edit URL and type name.
For backward compatibility, the typename will be retrieved from layers with priority on typename written in search entry and, if not present, a fallback to layer's name.

Summary

Consolidated acceptance criteria

• Data model: search.typeName separate from layer.name, with fallback (priority to search.typeName if set, otherwise layer.name) for backward compatibility
• search.url editable (absorbed from A way to edit urls of layers #12571): the linked WFS service's URL
• Pre-check on points to review (original AC "used in every place the layer's wfs is used"): epics/wfsquery.js, FilterUtils, dependenciesToFilter, layerdownload, layerfilter, geoProcessing, IdentifyUtils, WFSLayerUtils
• Catalog: merge search.typeName in recordToLayer, with a service-level default (service.layerOptions.search.*) should apply the typeName too.
• GUI: new "WFS linked service" section in Layer Properties: General tab, for WMS layers add/remove/edit URL and typeName of search.url and search.typeName as for the Mockup, except for the title.

[tdipisa]

@offtherailz we should consider exposing the URL field indicating from where the layer is loaded also for all other data types supported, where applicable. Please provide some feedback for that and maybe also update ACs.