Allow field groups on record page to default to collapsed

[bananasharkme]

On the record page, field groups rendered by FieldsWidgetGroupContainer
always start expanded. The component accepts a defaultExpanded prop, but
FieldsWidget.tsx never passes it for user-defined groups — only the
auto-generated "More (N)" hidden-fields group is collapsed by default.

For objects with many groups this is painful. In our workspace the Person
card has 10 groups. Opening a person means scrolling past
the entire fields card before reaching relation widgets (Company,
Opportunities, etc.).

Users can collapse groups manually, but because the state is local
useState it resets on every page reload — so every visit restarts the
scroll problem.

Proposal

Add a defaultExpanded: Boolean property to each group in
UpsertFieldsWidgetInput and the stored FieldsWidgetConfiguration.
Default to true so existing workspaces behave identically.

Surface a toggle in the group configuration UI
(FieldsConfigurationGroupEditor.tsx) so workspace admins can pick
per-group which sections start collapsed.

Pass it through in FieldsWidget.tsx:

  <FieldsWidgetGroupContainer                                                                                                            
    title={group.name}                                        
    defaultExpanded={group.defaultExpanded ?? true}
  >                                                                                                                                      
    …
  </FieldsWidgetGroupContainer>                                                                                                          

Scope of this PR

• Backend: extend the group DTO in UpsertFieldsWidgetInput and
  FieldsWidgetConfiguration with defaultExpanded: boolean
  (default true).
• Frontend:
  • FieldsWidget.tsx — forward the prop.
  • FieldsConfigurationGroupEditor.tsx — add a "Collapsed by default"
    toggle.
• Storybook: new story covering collapsed-by-default groups.
• No DB migration — widget groups are stored as JSON on the page
  layout widget, so an added optional field is backward compatible.

[Bonapara]

Thanks for the idea! I agree this would add value