Audit follow-up: Relationship and host-folder fields mark content dirty during async initial load

Parent epic: #36004

Finding

The audit reports relationship and host-folder fields emit onChange / onTouched during async initial load without a load-state gate. Category and file fields reportedly already gate on LOADED.

Report references: dotcms-ui/src/app/portlets/dot-edit-content/components/fields/dot-relationship-field/dot-relationship-field.component.ts:199-202, dotcms-ui/src/app/portlets/dot-edit-content/components/fields/dot-relationship-field/dot-relationship-field.component.ts:377-384, host-folder-field.component.ts:67-100

Potential impact

Users may see a spurious unsaved-changes prompt after only viewing content.

Suggested validation

Open content with relationship and host-folder fields in a slow/async-load scenario and confirm whether the form becomes dirty without user edits.

Possible fix

Mirror the existing category/file field load gating so initial async value hydration does not emit user-change/touched events.

Caveat

This was AI-found by Claude from .scratch/audit/REPORT.md. Please perform secondary validation of correctness, severity, and value before actioning.

Read the referenced relationship-field sections at dotcms-ui/src/app/portlets/dot-edit-content/components/fields/dot-relationship-field/dot-relationship-field.component.ts:199-202 and :377-384, plus host-folder-field.component.ts:67-100. Compare their load handling with the category and file fields, then reproduce a slow async initial load. Done means confirming whether the form becomes dirty without edits and validating the proposed gating change.