Tree filter selects are labeled with the other request #491

Describe the bug

In tree-nodes.component.html the filters panel binds two labels to the other control. This is the same for WMS and WFS leaves.

• The select bound to filterGetFeatureInfo is labeled entity.layer.applyFilterToGetMap ("Aplicar filtros a las peticiones de mapas").
• The select bound to filterGetMap is labeled entity.layer.filterInfoByMunicipality ("Filtrar la información por municipio").

The spatial-selection select, bound to filterSelectable, uses entity.layer.filterSpatialSelectionByMunicipality. That binding was not part of this report.

To Reproduce

1. Open a tree leaf whose cartography has applyFilterToGetFeatureInfo and applyFilterToGetMap.
2. Open the filters panel.
3. Compare each formControlName with its mat-label.

Expected behavior

The GetFeatureInfo select is labeled as municipality information. The GetMap select is labeled as map requests.

Screenshots

None

Desktop

Confirmed in tree-nodes.component.html. Not tied to one OS or browser.

Smartphone

None

Additional context

Related context, not a fix for those issues: sitmun/sitmun-viewer-app#205 and #271.

The WMS-only import sentence on the folder metadata hints is a separate defect.