#6758 Fixed default custom editors and FeatureEditor config in context

[offtherailz]

Draft for tests that have to be refined/checked

Description

This PR solves the 2 points in this comment #6758 (comment)

1. Fix wrong import for default custom editors
2. Fix feature grid options callback issue due to multiple renders of plugins with different properties.
   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

What is the current behavior?

#6758

What is the new behavior?

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

For testing:

The problems that caused this PR are 2:

• The default custom editors "DropDownEditor", "NumberEditor" was not working anymore. (see https://mapstore.geosolutionsgroup.com/mapstore/docs/api/plugins#plugins.FeatureEditor)
• FeatureEditor (FeatureGrid) plugin wasn't able to load some custom configurations (expecially customEditorsOptions) in contexts (they work in localConfig)

So to test this you can create a context with the DropDownEditor and NumberEditor configured and check (example on dev ).

Trying to open the feature grid in edit mode (logged in as admin) you should be able to

• edit the attribute type ONLY with the values "FOREST", "MOUNTAIN", "DESERT", "LAKE", "SECRET" without possibility to keep it empty or any pagination in the dropdown.
• land attribute can not be a negative number

for a complete information and to replicate in other contexts.
The map in the example context contains the layer atlantis:landmarks and has this configuration of Attribute table:

{
 "cfg": {
      "customEditorsOptions": {
        "rules": [{
          "regex": {
            "attribute": "type",
            "typeName": "atlantis:landmarks"
          },
          "editor": "DropDownEditor",
          "editorProps": {
            "values": ["FOREST", "MOUNTAIN", "DESERT", "LAKE", "SECRET"],
            "forceSelection": true,
            "defaultOption": "FOREST",
            "allowEmpty": false
          }
        }, {
          "regex": {
            "attribute": "land",
            "typeName": "atlantis:landmarks"
          },
          "editor": "NumberEditor",
          "editorProps": {
            "minValue": 0
          }
        }]
      }
}

[offtherailz]

@tdipisa didn't put the milestone to this PR (should it be backported, so having a new minor, or not)?

[coveralls]

Coverage decreased (-0.01%) to 78.707% when pulling d980af9 on offtherailz:6758 into ae25991 on geosolutions-it:master.

[MV88]

a few comments
the PR is good other than that

[MV88]

why stringify and not !isEqual or deepEqual from lodash?

[offtherailz]

I'll replace it with a deepEqual maybe be more robust and predictable.

[MV88]

ok :)