feat: add SubForm component

[standeren]

Description

Add SubFrom component but hide it in component-list behind featureFlag.

If an app should have a subform component i the layout added manually the config will show, but, since Team Apps have not released the component yet any potential apps that have this component are using it for test-purposes.
When Team Apps release the component we should include the featureflag for the new config that we create.

@Annikenkbrathen Currently used the ClipBoard icon from Aksel Icons. But we can adapt it later.

Related Issue(s)

• #{issue number}

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 95.17%. Comparing base (a5b89eb) to head (fca2c45).
Report is 11 commits behind head on main.

Files with missing lines	Patch %	Lines
...tend/packages/ux-editor/src/data/formItemConfig.ts	50.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #13564      +/-   ##
==========================================
- Coverage   95.18%   95.17%   -0.01%     
==========================================
  Files        1470     1470              
  Lines       20235    20237       +2     
  Branches     2448     2449       +1     
==========================================
+ Hits        19260    19261       +1     
  Misses        870      870              
- Partials      105      106       +1     

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

[lassopicasso]

starting review

[lassopicasso]

Great work! 💪 I like how you've used the .filter(Boolean) technique to conditionally display the SubForm.

I have one comment below, and I’m also curious about how the new text keys, e.g. ux_editor.component_properties.summaryDelimiter, are being used. Could you provide some context on that?

[standeren]

Great work! 💪 I like how you've used the .filter(Boolean) technique to conditionally display the SubForm.

I have one comment below, and I’m also curious about how the new text keys, e.g. ux_editor.component_properties.summaryDelimiter, are being used. Could you provide some context on that?

It is a new property added for the subFrom-component. So we are able to render it with our autogenerated config since it is type: string, but we do not have a text for it from before 🤗 And it is used as described in the helpText:
"The value used to separate cells/elements in a summary view where rich layout is not available. Typically a comma, dash or similar."

We definetly should add translations for these, but I think there is a separate issue for that!

[lassopicasso]

It is a new property added for the subFrom-component. So we are able to render it with our autogenerated config since it is type: string, but we do not have a text for it from before 🤗

Thx for the explanation, @standeren ! I'm not that used to the autogenerated config 😄

[lassopicasso]

Nice solved with the updated test, @standeren 💪

[ErlingHauan]

Tested OK with and without feature flag 😊