Refactor DataFormLayout: Introduce getWrapper function for improved l…

[gigitux]

What?

Closes #74999

Refactor wrapper selection in DataFormLayout by extracting it into a getWrapper helper and clarifying fallback behavior when form.layout.type is missing or not resolvable.

Why?

The wrapper selection logic had become harder to follow and reason about. This change centralizes the decision in one place.

How?

Wrapper resolution now follows this order:

1. Use as when provided.
2. If form.layout.type is defined, use its registered wrapper, falling back to DEFAULT_WRAPPER.
3. If form.layout.type is not picked (for example, it is undefined), use the first field’s layout wrapper, falling back to DEFAULT_WRAPPER.

This mirrors the existing layout defaulting during normalization: fields without an explicit layout inherit the form layout, and when the form layout is not picked, the first field effectively drives the layout. The wrapper fallback now follows the same approach.

Field layout components are unchanged and still selected per-field via getFormFieldLayout( formField.layout.type )?.component.

Testing Instructions

1. Check the Card Layout Storybook.
2. Ensure that the gap across the cards is 24px.
3. Remove the layout: "card" from form object (

   gutenberg/packages/dataviews/src/dataform/stories/layout-card.tsx

   Lines 176 to 177 in 18573f2

   	layout: { type: 'card' },
   	fields: [

   )
4. Ensure that the gap across the cards is 24px.

[github-actions]

Flaky tests detected in 4736b3b.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/21405199806
📝 Reported issues:

• [Flaky Test] should hide a block completely by selecting "Omit from published content" #74883 in /test/e2e/specs/editor/various/block-hiding.spec.js