Update DragAndDropListItemContext to assign the correct id to the parent

[lassopicasso]

Description

This PR addresses an issue where drag and drop type properties incorrectly saves/moves to the root instead of its actual parent (type).

The issue stems from the fact that the listItemContext used in the useParentId hook isn't updated with itemId, leading it to default to the rootContext.id, which represents the main data model. This might possibly due to the sequencing of updating useContext(DragAndDropListItemContext).
To solve this I added <DragAndDropListItemContext.Provider/> to the function DragAndDropProvider so it can be used on a higher level.

Also removed some code that isn't used anymore, the useStates: expandedProps and expandedDefNodes

Related Issue(s)

• Dragging/dropping a field in a data model type moves that field out of the type and into the main data model #12518

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.70%. Comparing base (bbce0ca) to head (27274c4).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12589      +/-   ##
==========================================
+ Coverage   88.69%   88.70%   +0.01%     
==========================================
  Files        1288     1288              
  Lines       18534    18526       -8     
  Branches     2270     2269       -1     
==========================================
- Hits        16439    16434       -5     
+ Misses       1836     1834       -2     
+ Partials      259      258       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ghost]

LGTM 😄