Description

This PR introduces a new capability within the FeatureEditor plugin to handle fetching/paginated and displaying unique attribute values from a specified source layer for use in editing attributes of another (target) layer. This is achieved by introducing a new rule with the editor key CustomAutocompleteEditor within cfg.customEditorsOptions.rules.

Configuration Example:

{
            "name": "FeatureEditor",
            "cfg": {
                "customEditorsOptions": {
                    "rules": [{
                        "regex": {
                            "attribute": "SUB_REGION",
                            "typeName": "gs:us_states"
                        },
                        "editor": "CustomAutocompleteEditor",
                        "editorProps": {
                            "filterProps": {
                            "blacklist": [],
                            "maxFeatures": 3,
                            "queriableAttributes": ["COMUNE"],
                            "predicate": "ILIKE",
                            "typeName": "test:Linea_costa"
                            }
                        }
                    }]
                }
            }
          },

The PR includes:

• create CustomAutocompleteEditor component to be used for the new requirements [fetching/displaying atrribute values from layer to be used in another layer]. A new editor designed to leverage a configurable stream for fetching autocomplete suggestions for feature attribute fields.
• create custom stream 'createCustomPagedUniqueAutompleteStream' to fetch values
• add unit tests

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

Issue

#11143

What is the current behavior?

#11143

What is the new behavior?

User can now define rules into FeatureEditor plugin in localConfig.json to specify an external source layer and attribute from which autocomplete suggestions are fetched to be used in add new feature or edit an existing feature.

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information