Normalize layers/groups management in TOC #10247

[rowheat02]

Description

fixes: #10247.
Some old maps and exports have groups in legacy format which shows some bugs like those mentioned in #10247.
Old formats can be converted to new standard formats with UI-wise invisible default group as a parent of all groups.

legacyGroups = [
  { id: '1', name: 'Group 1' },
 { id: DEFAULT_GROUP_ID }
 ];

newStandardFormat=[
      {
          id: <DEFAULT_GROUP_ID>,
         name: <DEFAULT_GROUP_ID>,
        nodes: [
             { id: '1', name: 'Group 1' },
             { id: 'DEFAULT_GROUP_ID.DEFAULT_GROUP_ID' } // Unique UUID generated
         ],
        expanded: true
    }
 ]
 

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?

#10247
There are some interactivity bugs on TOC in old maps and exports.

What is the new behavior?

There are no interactivity bugs on TOC in old maps and exports.

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

[rowheat02]

@tdipisa

• This PR solves the bugs mentioned here Normalize layers/groups management in TOC  #10247
• Now the conversion is done considering groups from this map.https://dev-mapstore.geosolutionsgroup.com/mapstore/#/viewer/39079. Are there any other maps with TOC bugs to verify?

[tdipisa]

@allyoucanmap it seems @rowheat02 is waiting for your feedback to unblock and finalize this PR. Can you please have a look?

[allyoucanmap]

This changes in this PR are technically making the presented cases in the issue work but it's not addressing this part:

As part of this issue is definitely requested to provide also the necessary clean up for completely removing the concept of "default group" to make also old maps consistent with new TOC behaviors.

The solution provided is adding a group prefix to the default group resulting in a new group id (Default.Default) that it making it works someway.
We should instead understand the following:

• Why the default group has the sort handler blocked?
• Why the sort/move action used by the TOC is preventing the default to be moved?
• Why the sort/move action used by the TOC is preventing the layers to be placed in the root?
• Is it possible to remove the concept of Default group and place nodes (groups and layers) inside the TOC root?

We need to take this issue to really understand the problem related to groups and layers in TOC and if needed also refactor logic and component.
I think we could accept this PR only once we answered the questions above and there isn't other alternatives.

---

Side note:
Usually group ids in mapstore are following this structure parentGroupId.groupId but it seems with the proposed changes we are adding the following case, where group01 and group02 don't have a the parentId group:

[
    {
        "id": "Default",
        "name": "Default",
        "nodes": [
            {
                "id": "Default.Default",
                ...
            },
            {
                "id": "group01",
                ...
            },
            {
                "id": "group02",
                ...
            }
        ]
    }
]

We need also to understand and investigate why is this still working