feat: Remove featureflag multiple data models per task

[lassopicasso]

Description

This PR removes the feature flag: 'multipleDataModelsPerTask and the code related to this + updates tests.

What should be tested before merging this to main

Pre-Test Setup

1. Navigate to the Datamodell page
2. Create and generate several data models with distinct data model fields
3. Navigate to the Prosesser page
4. Create a new layoutset and bind it to a data model so it has a default data model

Test cases

1. Default data model binding for layout set
   a. Create a new layout set i prosesser
   b. Bind the layout set to a default data model
   c. Go to “Utforming” section and add a component
   d. Verify that the default data model is selected in the data model bindings for the component.

2. Select an Alternative Data Model in Data Model Bindings
   a. Confirm that you can select a data model other than the default in the data model bindings for a component.

3. Switch between data models in data model bindings
   a. Test switching between different data models in the data model bindings for a component
   b. Ensure the related data model fields are displayed correctly in the dropdown list for each selection.

4. Preview Functionality with non-default data models
   a. Verify that the preview functionality works as expected when a data model other than the default is selected.
   b. See releated issue: Preview Fails When Linking Component to Non-Default Data Model #14104

5. Layout configuration – correct bindings displayed
   a. In the layout configuration in “se siste endringer”:
   i. Check that the correct bindings are displayed when selecting data model fields for the default data model
   ii. Check that the correct bindings are displayed when selecting a non-default data model and one of its data model fields

Related Issue(s)

• Remove featureflag for multiple data models #13797

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)

[lassopicasso]

This may need to be set to blocked after review until this is solved #14104, to make sure that number 4 works,Preview Functionality with non-default data models.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.57%. Comparing base (ffec39a) to head (303add0).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14171      +/-   ##
==========================================
- Coverage   95.58%   95.57%   -0.02%     
==========================================
  Files        1869     1869              
  Lines       24237    24234       -3     
  Branches     2786     2785       -1     
==========================================
- Hits        23167    23161       -6     
- Misses        814      815       +1     
- Partials      256      258       +2     

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

[mlqn]

Nice work! 🚀 I just left suggestions to remove some console.log.

[lassopicasso]

Nice work! 🚀 I just left suggestions to remove some console.log.

Thx! :)

[mlqn]

Tested OK in dev! 🙂🚀 but I didn’t realize I had already done the CR, so I can’t add the second approval on this one 🫤

[Annikenkbrathen]

Hi! just tested doing the 5 five test cases ☺️ it looks good overall, but I have some comments!

case 1: tested OK!✅

case 2: It worked to switch between different data models in the data model bindings for a component, but when I switched to a data model that is used in another task/layoutset, the preview crashed. When I switched to an unused datamodel, it worked perfectly fine! If that is something we can't/won't fix, maybe we should explain what's happening?

case 3: tested OK!✅ I have one thought about the data model bindings select. It might seem a bit odd that it looks like a data model binding field named "choose data model field" is already selected when switching between data models. Wouldn't it be better to have an empty select with a validation message indicating that you need to choose a data model field instead?

case 4: Commented on this in case 2

case 5: Tested OK (as far as I understood it 😅)

[lassopicasso]

Thx for testing, @Annikenkbrathen! I will investigate case 2 and your other comments 🙂