feat(intent): honor major on to-one relations (off the list, still in the form)

[delchev]

What

A relation's major attribute was silently ignored. RelationIntent had no major field, and EdmIntentGenerator hardcoded widgetIsMajor="true" for every relation (both relationProperty and crossModelRelationProperty). So major: false on a manyToOne/oneToOne parsed without error but never dropped the dropdown from the entity list / document-items table.

Change

• RelationIntent: new major field (default true) + isMajor()/setMajor().
• EdmIntentGenerator: both relation emitters now emit widgetIsMajor from relation.isMajor().

The Harmonia detail-register columns loop already filters on widgetIsMajor, so a major: false relation now renders in the create/edit form and detail pane but not as a list/items-table column — the exact counterpart of a field's major: false (already supported). Default true preserves all existing behavior; the attribute is opt-in.

Motivation

Document line-item tables often want the FK dropdown in the add/edit dialog only, with a Depends-On-copied descriptive field shown as the single column instead (e.g. an invoice item auto-copying the Product's name into an editable Name, and hiding the raw Product column). That needs major: false on the relation, which this enables.

Test

EdmIntentGeneratorTest#relationMajorFalseEmitsWidgetIsMajorFalseAndDefaultsTrue — a local and a cross-model major: false relation emit widgetIsMajor=false; a default relation stays true. Full engine-intent unit suite green (214).

Docs follow-up (separate dirigible.io PR): extend the DSL reference note on major: false to say it applies to relations too.

🤖 Generated with Claude Code